summaryrefslogtreecommitdiff
path: root/libre/libosinfo
diff options
context:
space:
mode:
authorDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2022-04-19 06:25:32 +0200
committerDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2022-04-19 06:35:44 +0200
commit309c3e3525f552c267dd7215df8f9d5043ecf82b (patch)
tree9f6e5e9dfb28e6388a448175f5a25afad90633f6 /libre/libosinfo
parent2e95c7e1bddebd5c779d42123b5878d37663dc8f (diff)
downloadabslibre-309c3e3525f552c267dd7215df8f9d5043ecf82b.tar.gz
abslibre-309c3e3525f552c267dd7215df8f9d5043ecf82b.tar.bz2
abslibre-309c3e3525f552c267dd7215df8f9d5043ecf82b.zip
Import the CC0 1.0 license
Hyperbola also imported that license in their core repository and Eli Schwartz uses the Unlicense for pers PKGBUILDs, so using compatible licenses would enable more code sharing between various distributions using PKGBUILDs. In addition several contributors consider many of the PKGBUILDs not to be copyrightable (because they are very simple). Note that just adding a license without any clear statements associated with it brings some legal uncertainty. From the GPL howto[1]: "If a program has a copy of a license FOO alongside the source files, but doesn't have an explicit statement that “This program is released under license FOO,” that leaves room for uncertainty about whether the license FOO applies to the code of that program." so it's better to add statements somewhere to use that license. [1]https://www.gnu.org/licenses/gpl-howto.html Link: https://labs.parabola.nu/issues/2862 Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Diffstat (limited to 'libre/libosinfo')
0 files changed, 0 insertions, 0 deletions