From mboxrd@z Thu Jan 1 00:00:00 1970 From: Amin Bandali Subject: Re: Firefox 52's end of life, packaging Chromium Date: Thu, 30 Aug 2018 10:23:45 -0400 Message-ID: <878t4oylu6.fsf@aminb.org> References: <87ftyx35pw.fsf@lassieur.org> <87pny09rgo.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57385) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvNrY-0006Zc-Om for guix-devel@gnu.org; Thu, 30 Aug 2018 10:23:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvNrX-0001gi-ID for guix-devel@gnu.org; Thu, 30 Aug 2018 10:23:56 -0400 In-Reply-To: <87pny09rgo.fsf@elephly.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus , =?utf-8?Q?Cl=C3=A9ment?= Lassieur Cc: guix-devel@gnu.org Ricardo Wurmus writes: >> So the question is: can we push the Chromium package? I've read it's >> almost ready[2]. > > The TODO list for convenience: > > --8<---------------cut here---------------start------------->8--- > * There is still some data transmitted when starting the browser for the > first time. It seems related to the "domain_reliability" component. > * Remove remaining "Web Store" links. Currently I've only found it in > settings, under "accessibility" and "fonts". > * Opening settings transmits a bunch of data, the next version will > include the 'disable-translation-lang-fetch' patch from Inox. > * PDFium is built, but does not seem to work (the 'install' phase > probably needs tweaking). Might just disable it instead. > --8<---------------cut here---------------end--------------->8--- > > It would be *very* nice if the first and third items could be solved > before merging, but I don=E2=80=99t consider them blockers. Would someon= e like > to investigate one of these problems? > > As has been stated multiple times in the discussion of this evolving > patch set, we cannot guarantee privacy, but we can make attempts to > remove problems as they become known. This will remain an uphill battle > and in future iterations of this package we should try to integrate more > patches provided by other groups working on removing anti-features from > Chromium. I highly recommend looking into ungoogled-chromium [0], which "modifies Google Chromium to remove Google integration and enhance privacy, control, and transparency". It's not exactly a fork, but rather a series of patches and modifications they apply to each Chromium release. In terms of documentation, they have a high-level description of the various components and patches [1], and build instructions for a few platforms and distros [2]. There was also an attempt to make a nix package a while ago [3], which may be helpful to look at. [0]: https://github.com/Eloston/ungoogled-chromium [1]: https://github.com/Eloston/ungoogled-chromium/blob/master/docs/design.= md [2]: https://github.com/Eloston/ungoogled-chromium/blob/master/docs/buildin= g.md [3]: https://github.com/NixOS/nixpkgs/pull/30916 --=20 Amin Bandali | GNU webmaster | Grad student, UWaterloo https://aminb.org | https://gnu.org | https://aminb.org/uw GnuPG Key: CDDE 75F9 0353 8E71 813C DA27 D1FB A366 27D6 5876