summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
diff options
context:
space:
mode:
authorAlyssa Ross <hi@alyssa.is>2023-02-23 20:52:35 +0000
committerAlyssa Ross <hi@alyssa.is>2023-02-24 00:06:46 +0000
commitf9afd57302f342f7e72048ea77ed57aef61ffe48 (patch)
treebbe2d661c443f165a419dd22b7e1f259569e2508 /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
parent2d415debb770f5c47c611c0908a85288e7b7f7bb (diff)
Revert "llvmPackages_15: update licenses"
This reverts commit 386aba3115176b11eb49a0606e9dd17506273776. As I understand it from reading <https://llvm.org/docs/DeveloperPolicy.html#copyright-license-and-patents>, the structure of LLVM licensing is as follows: - They're in the process of relicensing to Apache-2.0 WITH LLVM-exception, but they haven't got permission to relicense all the code yet. This means that some of the code can be used under the new license, but not all of it, and it's difficult to know which is which. This license is therefore probably not useful yet, until the relicensing effort is commit. - While the relicensing effort is ongoing, code being contributed to LLVM has to have permission to be used under the old and new licensing schemes. Since the new licensing scheme can't be used for all code yet, it only makes sense to use LLVM's code under the old licensing scheme at the moment. - The old licensing scheme is that code for the LLVM components we care about is all available under the NCSA license, and some components are optionally available under a different license, usually the MIT license, instead. So I think we should go back to just listing NCSA, or NCSA/MIT, and forget about the new license until it actually becomes useful, i.e. LLVM's relicensing effort is complete.
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions