From mboxrd@z Thu Jan 1 00:00:00 1970 From: bill-auger Subject: Re: [GNU-linux-libre] [PATCH] gnu: Add ungoogled-chromium. Date: Tue, 19 Feb 2019 15:45:33 -0500 Message-ID: <20190219154533.5e2e962b@parabola> References: <20190202192023.22087-1-mbakke@fastmail.com> <87k1igpwk8.fsf@dismail.de> <20190203235204.63970587@parabola> <87sgx3mbcq.fsf@gnu.org> <87tvhf5f8d.fsf@dustycloud.org> <20190216030021.374f4c82@parabola> <87va1kav33.fsf@posteo.net> <87lg2f5wqk.fsf@posteo.net> <87k1hz5wh8.fsf@posteo.net> <20190216203933.218dfb67@parabola> <87bm3axcyl.fsf@elephly.net> <20190218070557.12fc0471@parabola> <87wolxyzx4.fsf@nckx> <5345711550517740@myt1-e20b74e6250c.qloud-c.yandex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:54076) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gwCHX-0004fP-QT for guix-devel@gnu.org; Tue, 19 Feb 2019 15:46:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gwCHW-0007Lk-Uq for guix-devel@gnu.org; Tue, 19 Feb 2019 15:46:23 -0500 Received: from palegreen.birch.relay.mailchannels.net ([23.83.209.140]:29443) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gwCHW-0007Ke-DD for guix-devel@gnu.org; Tue, 19 Feb 2019 15:46:22 -0500 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 9EF5F6833B4 for ; Tue, 19 Feb 2019 20:46:19 +0000 (UTC) Received: from pdx1-sub0-mail-a67.g.dreamhost.com (unknown [100.96.30.62]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 3E9A9683A6C for ; Tue, 19 Feb 2019 20:46:19 +0000 (UTC) Received: from pdx1-sub0-mail-a67.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a67.g.dreamhost.com (Postfix) with ESMTP id 00AC27F1CD for ; Tue, 19 Feb 2019 12:46:19 -0800 (PST) Received: from parabola (75-138-186-142.dhcp.oxfr.ma.charter.com [75.138.186.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: bill-auger@peers.community) by pdx1-sub0-mail-a67.g.dreamhost.com (Postfix) with ESMTPSA id 851B97F187 for ; Tue, 19 Feb 2019 12:46:18 -0800 (PST) In-Reply-To: <5345711550517740@myt1-e20b74e6250c.qloud-c.yandex.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: guix-devel@gnu.org On Mon, 18 Feb 2019 20:22:20 +0100 Simon wrote: > seems to be shifting to a meta rather than about the state of > chromium itself simon - i would like to explain that the reason for that confusion, is because this thread got cross-posted on multiple mailing lists the chromium browser is the topic of the thread on the guix mailing list - but that "meta" divergence as you described it, is entirely the purpose of the FSDG workgroup - the central concern on that list today, is not chromium itself, but is enticing guix to discuss what has been done to liberate chromium with the group; so that the recipe can be peer reviewed and possibly be recommended to other distros the folks reading the FSDG list would not describe that as a divergence, but as the latest attempt to make progress on a long standing problem that affects all FSDG distros equally