Packaging request #2512

ungoogled-chromium with Guix recipe: is it a go?

dllud - 4 months ago - . Updated 4 months ago.

% Done:



I just found out that Guix (a FSDG compliant distro) distributes ungoogled-chromium after running it through a build recipe that removes a few extra files.

On Guix mailing list there is the following bold statement:

To the best of our knowledge, ungoogled-chromium as packaged in guix is completely free

Would Parabola devs be willing to replicate Guix build recipe and distribute ungoogled-chromium on Parabola?
Or are there further concerns that haven't been addressed by Guix?

This is tangentially related to #1167, which deals mostly with qt5-webengine. If Guix approach is deemed valid perhaps it could serve as a base for qt5-webengine. Although I reckon that qt5-webengine, being much more limited in scope, ought to include a smaller subset of Chromium than ungoogled-chromium (which is a fully featured browser).


purism.log (2.82 KB) purism.log IRC logs from #purism dllud, 2019-10-26 06:06 PM

Related issues

Related to Packages - Freedom issue #1167: [chromium][qt5-webengine][electron] QTWebgine/Electron embeds "entire Chromium platform"confirmed




Updated by bill-auger 4 months ago

  • Priority changed from bug to wish

yes indeed that would be awesome, IF the guix recipe were generally accepted to be FSDG-fit; but currently, only guix has deemed it to be so - the standing consensus of the FSDG work-group is that neither chromium nor any of its derivatives are convincingly within the FDSG; and by Feb 2018, the one FSDG distro that still distributed it (pureos), had removed it from their standard repos for this reason, closing a long standing freedom-bug report on their bug tracker

even if we wanted chromium, the blocker is that it is on the "List of software that does not respect the Free System Distribution Guidelines"; which offers recommended liberation procedures, and is among the FSDG criteria - if the guix recipe were acceptable, parabola probably would have done the same years ago, before guix and pureos existed; and today it would be guix and pureos duplicating the parabola recipe - the key point though, is that it would not be "the parabola recipe" - it would be presented to the FSDG work-group for evaluation, and if the consensus were that it was an acceptable liberation procedure, then it would become the standard FSDG recommendation for any FSDG distro that wants to package chromium - as of today, no such liberation procedure exists; and the DSFG "Recommended Fix" is still: "Remove program/package. Use GNU IceCat, or equivalent"

until the FSDG recommendation for chromium validates the guix recipe, this packaging request reduces to a duplicate of the original from 7 years ago #140; because no new information has come to light since that time, which would change the FSDG recommendation - if this issue was as easily resolved as guix contends it to be; parabola probably would have added chromium 7 years ago


Updated by bill-auger 4 months ago

  • Related to Freedom issue #1167: [chromium][qt5-webengine][electron] QTWebgine/Electron embeds "entire Chromium platform" added

Updated by oaken-source 4 months ago

frankly, the entire thing is pretty ugly. has always been.

and the involvement of guix in this mess hasn't made anything prettier. I'd be disinclined to trust that whatever guix has done here further than I can throw a chromebook.


Updated by dllud 4 months ago

bill-auger: thanks for the detailed reply.

PureOs added Chromium back again. The replies on the issue imply that and GNUtoo confirmed, a few days ago (Oct 21), that it is available on the repos for both amber and byzantium. I am attaching the relevant IRC logs.

Has Guix presented ever their solution to the FSDG work-group for evaluation? If so, could you point me there? Thanks!


Updated by bill-auger 4 months ago

FWIW, to pre-empt any rebuttals, i contend that this is not an issue for parabola to decide alone; so there is little point to discuss it on this bug tracker - if anyone is truly concerned about resolving this conflict, the appropriate venue to discuss it is the FSDG mailing list - i have raised this issue on that list again just recently (actually, quiliro did); and everyone is invited to voice their opinion


Updated by bill-auger 4 months ago

no, guix did not present their work to the work-group - they entered the conversation briefly after some people had been cross-posting to the mailing lists of guix, the FSDG, and GNU, in opposition to the decision to add chromium to guix - when asked to help the work-group to resolve the conflict with the FSDG, the suggestion was that people should read the guile code for the package

not everyone in the work-group is a programmer though; so someone would need to read and understand it, then explain it to the group in plain words, so that everyone can make an informed decision - that is yet to happen though

if the group decides it is acceptable, and most importantly to convnice the FSF to accept it, then it could become the standard recommendation; which would also be in plain words - and if the work-group decides that it is not acceptable, then most importantly, the FSF should step in and ask all endorsed distros to remove it, or revoke their endorsement

i have no strong preference, aside from deferring the matter to the FSDG work-group - any of those outcomes would be fine by me; but the current situation sucks (pardon my french), and it doesnt seem likely that any of those resolutions will come to pass any time soon

Also available in: Atom PDF