From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: Firefox 52's end of life, packaging Chromium Date: Sun, 02 Sep 2018 15:54:38 +0200 Message-ID: <87lg8kj97l.fsf@fastmail.com> References: <87ftyx35pw.fsf@lassieur.org> <87pny09rgo.fsf@elephly.net> <878t4oylu6.fsf@aminb.org> <87pnxxfgzc.fsf@gnu.org> <20180901173152.czqoq66rzrslrwif@abyayala> <87lg8larng.fsf@aminb.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33094) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fwSr6-0007V7-HH for guix-devel@gnu.org; Sun, 02 Sep 2018 09:56:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fwSqo-0000pN-Fz for guix-devel@gnu.org; Sun, 02 Sep 2018 09:55:45 -0400 In-Reply-To: <87lg8larng.fsf@aminb.org> 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: Amin Bandali , Nils Gillmann , Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org, =?utf-8?Q?Cl=C3=A9ment?= Lassieur --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Amin Bandali writes: > Nils Gillmann writes: > >> Please read into the chromium thread or search locally through it - >> Marius already had some comments on ungoogled-chromium. Our chromium >> browser is not just chromium taken from upstream. Many (maintained) >> patches are taken and applied. > > Thanks for mentioning this. You seem to be referring to the [0] > message and the [1] package from last year, which I hadn't seen > before. > > To quote Marius, > > ,----[ Marius Bakke ] > | I actually picked most of the patches from ungoogled-chromium (which > | includes inox and iridium), but skipped "high maintenance" ones. This > | started as an attempt to package that very project, but they were > | lagging too far behind upstream IMO. > |=20 > | FSDG problems is the reason I haven't advertised it. At the very least, > | the Google integrations should be disabled and analytics removed (but > | Chromium can't currently build without either). I think if most of the > | "FIXMEs" are resolved upstream, it might be eligible for a free distro. > |=20 > | Now that the cat is out of the box, feel free to send patches somewhere > | and I'll incorporate them in the branch :-) > `---- > > With regards to FSDG problems, I wonder what the status is today, > considering that ungoogled-chromium's patch sets seem to have > grown a fair bit in number [2], and might be already addressing > some of the issues. > > As for the "lagging too far behind upstream" issue, that doesn't > seem to be the case anymore: looking at releases on [3] and [4] > it looks like ungoogled-chromium's latest shipped release matches > the latest released chromium version. Granted, I have noticed in > the past for ungoogled-chromium to lag behind the latest release > by a week or two, that'd still be better compared to the current > situation with respect to the current Firefox/IceWeasel release. Indeed, Ungoogled have catched up pretty well and is a viable choice nowadays. If it helps get Chromium into Guix I'm all for it. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAluL654ACgkQoqBt8qM6 VPoW+ggAmmc6TPczH0AFs0Sy5SIRENNmwTnz6ZyF/7rvNCd0oKTjGGWSb3OQRCCF frqKzX0dlEcAFUYa4HLdkqTxdpJNkGWkASC02KeIxlG1Yt1HZZvG0hbnJ8uOPqwi pQPtGZdHgR0gUhJk8YeThyzxVVRHvCG+a+CuWdUiTq3+5Q33uK2w4VhBC+vOBwVm EIjmvCZ1/RXBUtGdnSA3ZV3ZmVQIHyYQi8ZFn4ECxYh/qwcgXXCP5ry/s3QZAF+G lpMe9015psRie/5OT/svfzz5rlb7NRL3QauhKlMZvh825kJoihO9qbqkEV3k/QDC o98PJsMx3kZA14CWCvhujFAKgsMyLw== =+/9+ -----END PGP SIGNATURE----- --=-=-=--