Christopher Lemmer Webber writes: > Hello! I'd like to speak up in favor of getting Chromium merged into > Guix master. As a web developer, sometimes I have to test things > against multiple browsers. Having Chromium in GuixSD would help me out > a lot. > > It looks like a mountain of hard work has been put into this. Could we > get it merged rather than have that work languish? Hello! I use this browser a lot, so it's hardly languishing. There was a recent discussion[0] about the Pale Moon browser, where it was pointed out that the FSDG[1] requires that any third-party repositories must be committed to only free software. [0] https://lists.gnu.org/archive/html/guix-devel/2018-03/msg00319.html [1] https://www.gnu.org/distros/free-system-distribution-guidelines.html#license-rules Unfortunately there are UI links to the Chrome "Web Store" still. It's not possible to install from it without setting the CHROMIUM_ENABLE_WEB_STORE variable, but I'm not sure if that is sufficient. It's unfortunate if an unsuspecting user stumbles into the Web Store and tries to install something (free or not) and only then finds out that it does not work. The other remaining issue is that some data is sent to Google whenever you start the browser for the first time. I don't think that's a blocker, but it's certainly something we should aim to fix. Attached are updates for 66. The first is an interdiff from the previous 65 patch; the other is the full "squashed" patch for convenience. New in this version: * The snippet will now error if a preserved directory is not present. * Chromium again requires a git revision of libvpx. * The "safe browsing" feature requires the nonfree "unrar" program(!!), as such it has been compiled out. Luckily "Inox" already had a patch to make the thing actually build with that flag disabled. * Cosmetic rearrangement of patches to follow Debian and Inox patch order.