From mboxrd@z Thu Jan 1 00:00:00 1970 From: Amin Bandali Subject: Re: [PATCH] gnu: Add ungoogled-chromium. Date: Sat, 16 Feb 2019 14:27:18 -0500 Message-ID: <87tvh3wn3d.fsf@aminb.org> 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> <878syfwx59.fsf@fastmail.com> <8736onyabo.fsf@aminb.org> <875ztjwv5a.fsf@fastmail.com> 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: <875ztjwv5a.fsf@fastmail.com> (Marius Bakke's message of "Sat, 16 Feb 2019 17:33:21 +0100") 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: Marius Bakke Cc: guix-devel@gnu.org, gnu-linux-libre@nongnu.org List-Id: guix-devel.gnu.org Marius, On 2019-02-16 5:33 PM, Marius Bakke wrote: [...] > > Can you point out one or more files with an unclear license? Do we have > any reason to distrust what's written in the LICENSE file? > I don=E2=80=99t have a direct example of one such file off top of my head, = but looking at the large reported chromium issue[1], I see there are a number of open blocking issues linked to that one. Also, I was looking at [2] and [3] from a little over a year ago, which included the results of running licensecheck on the chromium tree, but I wasn=E2=80=99t able to download any of the resulting txt files there. So I thought I=E2=80=99d cl= one a fresh copy of chromium and run licensecheck from the Debian Stretch repo on all the files as follows: git clone --depth 1 https://chromium.googlesource.com/chromium/src.git cd src git rev-parse HEAD # result: eda06a0b859a08d15a1ab6a6850e42e667530f0b licensecheck -c '.*' -r * > ../licensecheck-chromium-eda06a0b859a.txt I=E2=80=99ve attached a gzipped version of the above text file. Granted, t= here are caveats: firstly, that the above invocation of licensecheck examines /all/ of the files in the repo, including test html files which are not relevant and should be filtered out; and secondly, the output contains a very large number of =E2=80=9CUNKNOWN=E2=80=9D results which may be false p= ositives. Link [3] mentioned running FSD Script Aid on the chromium tree as well, but I don=E2=80=99t have enough time at the moment to do so. Hope this is of some help. [1]: https://bugs.chromium.org/p/chromium/issues/detail?id=3D28291 [2]: https://lists.gnu.org/r/directory-discuss/2017-11/msg00014.html [3]: https://directory.fsf.org/wiki/Talk:Chromium Best, amin