From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Lemmer Webber Subject: Re: [PATCH] gnu: Add ungoogled-chromium. Date: Thu, 07 Feb 2019 18:52:02 -0500 Message-ID: <87tvhf5f8d.fsf@dustycloud.org> References: <20190202192023.22087-1-mbakke@fastmail.com> <87k1igpwk8.fsf@dismail.de> <20190203235204.63970587@parabola> <87sgx3mbcq.fsf@gnu.org> Reply-To: Workgroup for fully free GNU/Linux distributions Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-reply-to: <87sgx3mbcq.fsf@gnu.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gnu-linux-libre-bounces+gldg-gnu-linux-libre=m.gmane.org@nongnu.org Sender: "gnu-linux-libre" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org, gnu-linux-libre@nongnu.org, 28004@debbugs.gnu.org List-Id: guix-devel.gnu.org Ludovic Court=C3=A8s writes: > Hi bill-auger, > > bill-auger skribis: > >> re: https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00009.html >> >> i would like to remind readers of the guix-devel list that it was >> discussed some months ago, why no FSDG distros currently distribute >> chromium[1] - it appeared at that time, that most people in that >> discussion were in agreement that chromium should not be included in >> guix; and marius was instead hosting it in a private repo, as not to >> taint the main guix repos with dubious software - has there been a >> notable break-through since then? > > It=E2=80=99s not entirely clear to me what the problems are, to be honest. > Marius listed specific issues that were addressed by the patches; others > then pointed out at additional issues that ungoogled-chromium fixes, > which Marius took into account; what=E2=80=99s left now? > > I understand you=E2=80=99re skeptical about Chromium, but we cannot base > decisions based on vague skepticism. If you know of issues that are > still unaddressed, please do list them. > > I=E2=80=99d also like to stress that, if Chromium is eventually included = in > Guix, we are committed to fixing it or removing it should someone later > discover that it does not comply with the FSDG (that=E2=80=99s the =E2=80= =9CCommitment > to Correct Mistakes=E2=80=9D section of FSDG.) +1 ... If concrete problems are found, by all means those should be raised and addressed. Otherwise I really think we ought to merge this work.