[llvm-dev] Ticket 46201 - Missing LLVM NOTICE file is making redistributing LLVM difficult

[Neil Nelson via llvm-dev]

Jukka's https://bugs.llvm.org/show_bug.cgi?id=46201 has

    Our release management at Unity are finding it difficult legal wise to redistribute LLVM,
    as LLVM itself does not carry such a NOTICE file that would list the third party licenses of LLVM itself.
    Such third party content is found for example at least in the following files

    - llvm/lib/Support/COPYRIGHT.regex
    - llvm/lib/Support/MD5.cpp
    - llvm/lib/Support/xxhash.cpp
    - llvm/utils/benchmark/LICENSE
    - llvm/utils/unittest/googlemock/LICENSE.txt
    - llvm/utils/unittest/googletest/LICENSE.TXT

    (in addition to the main license in llvm/LICENSE.txt)

The files under llvm/lib/Support may need a LICENSE.txt. Each of the 
three files has a different license. The apparent remaining issue is how 
to have a LICENSE.txt in this case and if there are similar cases not 
accounted for.

Neil Nelson

On 6/5/20 10:58 AM, Chris Lattner via llvm-dev wrote:
> Hi Jukka,
>
> We discussed this with the LLVM Foundation board.  While we think 
> there is high utility to providing such a NOTICES file, we don’t know 
> of a way to keep it up to date, and don’t want to be providing 
> incorrect information for such an important topic.
>
> That said, the llvm/LICENSE.TXT checked into the code has this 
> information about how to identify third party licenses in the code 
> base.  I hope this is enough to help with your analysis.
>
> ==============================================================================
> Software from third parties included in the LLVM Project:
> ==============================================================================
> The LLVM Project contains third party software which is under 
> different license
> terms. All such code will be identified clearly using at least one of two
> mechanisms:
> 1) It will be in a separate directory tree with its own `LICENSE.txt` or
> `LICENSE` file at the top containing the specific license and restrictions
> which apply to that software, or
> 2) It will contain specific license and restriction terms at the top 
> of every
> file.
>
> Thanks!
>
> -Chris
>
>
>
>> On Jun 4, 2020, at 10:51 PM, Jukka Jylänki via llvm-dev 
>> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>>
>> Hello all,
>>
>> I was asked to bring attention to this LLVM ticket to the mailing list:
>>
>> https://bugs.llvm.org/show_bug.cgi?id=46201 - Missing LLVM NOTICE file
>> is making redistributing LLVM difficult.
>>
>> It was recently noted by our legal review in release management that
>> LLVM third-party licenses are scattered over different files, which
>> complicates faithful license-preserving redistribution of LLVM to our
>> users. Having a grouped license declaration of would make building
>> redistributables easier.
>>
>> Best,
>> Jukka
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200605/b3619325/attachment.html>