From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: licenses/, profiles/
Date: Fri, 5 Jul 2019 10:43:14 +0000 (UTC) [thread overview]
Message-ID: <1562323329.cc6ef7709aa0b584c163c208cacb3e48d5d222f7.ulm@gentoo> (raw)
commit: cc6ef7709aa0b584c163c208cacb3e48d5d222f7
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 5 10:34:46 2019 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri Jul 5 10:42:09 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cc6ef770
licenses: Add JSON license for dev-java/json.
Same as MIT, but with an additional clause "The Software shall be
used for Good, not Evil." This is a usage restriction which makes the
license non-free. It doesn't prevent binary redistribution, so add it
to that license group.
https://www.gnu.org/licenses/license-list.html#JSON
https://spdx.org/licenses/JSON.html
Bug: https://bugs.gentoo.org/689314
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
licenses/JSON | 22 ++++++++++++++++++++++
profiles/license_groups | 2 +-
2 files changed, 23 insertions(+), 1 deletion(-)
diff --git a/licenses/JSON b/licenses/JSON
new file mode 100644
index 00000000000..e26c1db7f74
--- /dev/null
+++ b/licenses/JSON
@@ -0,0 +1,22 @@
+Copyright (c) 2002 JSON.org
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+The Software shall be used for Good, not Evil.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
diff --git a/profiles/license_groups b/profiles/license_groups
index 2f21e6021f7..186eb05df64 100644
--- a/profiles/license_groups
+++ b/profiles/license_groups
@@ -65,7 +65,7 @@ FREE @FREE-SOFTWARE @FREE-DOCUMENTS
# - IF (and only if) there is an explicit inclusion requirement,
# USE=bindist MUST cause a copy of the license to be installed
# in a file location compliant with the license
-BINARY-REDISTRIBUTABLE @FREE bh-luxi bonnie Broadcom Dina freedist intel-ucode ipw2100-fw ipw2200-fw ipw3945 linux-fw-redistributable LSI-tw_cli MicroChip-SDCC no-source-code NVIDIA-r1 qlogic-fibre-channel-firmware shmux SmartLabs sun-jlfgr unRAR
+BINARY-REDISTRIBUTABLE @FREE bh-luxi bonnie Broadcom Dina freedist intel-ucode ipw2100-fw ipw2200-fw ipw3945 JSON linux-fw-redistributable LSI-tw_cli MicroChip-SDCC no-source-code NVIDIA-r1 qlogic-fibre-channel-firmware shmux SmartLabs sun-jlfgr unRAR
######################################################################
next reply other threads:[~2019-07-05 10:43 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 10:43 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-05 11:34 [gentoo-commits] repo/gentoo:master commit in: licenses/, profiles/ Andrew Ammerlaan
2024-06-11 16:41 Ulrich Müller
2024-05-01 14:14 Michał Górny
2023-04-12 13:09 David Seifert
2023-01-21 16:40 Ulrich Müller
2023-01-12 11:48 Ulrich Müller
2022-08-31 9:58 Ionen Wolkens
2022-06-22 8:41 Michał Górny
2022-04-05 19:50 Ulrich Müller
2022-02-12 16:50 Michał Górny
2021-09-08 6:29 Robin H. Johnson
2021-06-27 7:26 Ulrich Müller
2021-05-13 16:12 Ulrich Müller
2021-05-09 4:42 Sam James
2021-01-08 17:34 Ulrich Müller
2020-11-15 9:35 Michał Górny
2020-10-25 17:39 Andreas K. Hüttel
2020-10-10 6:07 Michał Górny
2020-09-25 14:32 Michał Górny
2020-06-09 17:21 Ulrich Müller
2020-03-25 11:17 Joonas Niilola
2020-03-21 10:57 Ulrich Müller
2020-02-11 7:39 Ulrich Müller
2020-01-18 11:50 Ulrich Müller
2019-12-28 10:18 Ulrich Müller
2019-12-11 19:18 Ulrich Müller
2019-12-01 21:23 Ulrich Müller
2019-11-03 9:29 Michał Górny
2019-09-15 14:58 Michał Górny
2019-05-16 6:37 Ulrich Müller
2019-04-24 21:20 Ulrich Müller
2019-04-21 9:17 Ulrich Müller
2018-09-13 19:23 Ulrich Müller
2018-08-17 20:04 Ulrich Müller
2018-03-05 19:21 Ulrich Müller
2018-02-06 13:52 Eray Aslan
2017-11-23 22:14 Ulrich Müller
2017-09-14 17:09 Ulrich Müller
2017-08-19 6:56 Ulrich Müller
2017-06-07 10:50 Tony Vroon
2017-06-06 6:52 Ulrich Müller
2017-04-20 9:06 Ulrich Müller
2017-04-20 9:06 Ulrich Müller
2017-03-18 9:09 Michael Palimaka
2017-01-14 18:14 Michał Górny
2016-10-25 22:48 Ulrich Müller
2016-10-18 16:59 Ulrich Müller
2016-08-03 20:59 Austin English
2016-06-26 22:40 Ulrich Müller
2016-06-09 0:40 Ulrich Müller
2016-05-01 20:06 Ulrich Müller
2016-05-01 17:33 Ulrich Müller
2016-03-19 11:19 Ian Delaney
2016-01-19 8:37 Patrice Clement
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1562323329.cc6ef7709aa0b584c163c208cacb3e48d5d222f7.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox