From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Cl=C3=A9ment?= Lassieur Subject: Re: Firefox 52's end of life, packaging Chromium Date: Thu, 30 Aug 2018 10:54:39 +0200 Message-ID: <8736uw2q0g.fsf@lassieur.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]:49789) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvIj3-0003wR-8K for guix-devel@gnu.org; Thu, 30 Aug 2018 04:54:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvIiw-0003q1-Of for guix-devel@gnu.org; Thu, 30 Aug 2018 04:54:49 -0400 Received: from mail.lassieur.org ([83.152.10.219]:45702) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fvIiw-0003pK-9j for guix-devel@gnu.org; Thu, 30 Aug 2018 04:54:42 -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 Cc: guix-devel@gnu.org Hi Ricardo, Thank you for your reply. Ricardo Wurmus writes: > Hi Cl=C3=A9ment, > >> Firefox 52 isn't supported anymore upstream[1] and we don't have a >> package for Firefox 60. Currently the only alternative is Epiphany but >> it's close to unusable (it crashes every 5 minutes, and sometimes >> freezes my computer). > > I=E2=80=99m surprised to hear that you=E2=80=99ve had problems with Epiph= any. I=E2=80=99m using > it daily for dozens of tabs and I recommend it to people who cannot use > Icecat. It=E2=80=99s difficult to send good bug reports when the browser > freezes the computer, of course, but it would be helpful to get more > information about these crashes, if you can reproduce them. Sure, I'll report them when I find the time. >> 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. It's not clear to me :-) Does it mean we can merge? > 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. > > Thanks to Marius for driving the evolution of this patch set through > multiple upgrades and bringing it to a usable state! > > My personal recommendation is to use Epiphany if possible (and Icecat > once version 60 is ready) and to be careful with Chromium. Thank you for this important information. Cl=C3=A9ment