summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUlrich Müller <ulm@gentoo.org>2022-07-24 19:15:42 +0200
committerUlrich Müller <ulm@gentoo.org>2022-07-25 18:08:46 +0200
commit92bb5e10171165b681c3ec526d90a1508e6dc9fa (patch)
treeba8e364e2538660c98f726e5779c80c834a2675f /ebuild-format.rst
parentinstalled-files: Restrict find to regular files (diff)
downloadpolicy-guide-92bb5e10171165b681c3ec526d90a1508e6dc9fa.tar.gz
policy-guide-92bb5e10171165b681c3ec526d90a1508e6dc9fa.tar.bz2
policy-guide-92bb5e10171165b681c3ec526d90a1508e6dc9fa.zip
other-metadata: Sync with the updated LICENSE policy in the devmanual
See commit 4a74d85 in the proj/devmanual repository: By the FSF's definition (see for example GPL-3): "The 'Corresponding Source' for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities." It makes much sense to apply this as a general definition. Applying it only to GPL licensed packages would mean: - We would need another case distinction, making the rules for LICENSE even more complicated. - As an example, consider a MIT licensed package with a CDDL licensed (i.e., GPL incompatible) build script: If that package was a library, then it couldn't be linked against a GPL licensed package, whereas a LICENSE variable listing only MIT would falsely indicate that it could. Closes: https://bugs.gentoo.org/860552 Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'ebuild-format.rst')
0 files changed, 0 insertions, 0 deletions