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’t 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’t able to download any of the resulting txt files there. So I thought I’d clone 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’ve attached a gzipped version of the above text file. Granted, there 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 “UNKNOWN” results which may be false positives. Link [3] mentioned running FSD Script Aid on the chromium tree as well, but I don’t 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=28291 [2]: https://lists.gnu.org/r/directory-discuss/2017-11/msg00014.html [3]: https://directory.fsf.org/wiki/Talk:Chromium Best, amin
