<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Missing LLVM NOTICE file is making redistributing LLVM difficult"
href="https://bugs.llvm.org/show_bug.cgi?id=46201">46201</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Missing LLVM NOTICE file is making redistributing LLVM difficult
</td>
</tr>
<tr>
<th>Product</th>
<td>Documentation
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>General docs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jujjyl@gmail.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>The Apache license commonly is associated with a NOTICE file stating Derivative
licenses and third party licenses, and modifications.
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)
Legal teams may have a difficult time searching through subdirectories of a
large project for licensing information, hence having the relevant information
in one core file in project root is preferred. (also development teams building
redistributable packages may have difficulties finding all the needed licenses
to bundle)
Our release management has been proposing of crafting such a NOTICE file on
behalf of LLVM, and redistributing LLVM with such a NOTICE file as part of
Unity LLVM packages, but writing license information on behalf of another
project does not seem appropriate, so would be better if LLVM carried a NOTICE
file grouping together the third party licenses?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>