From: Eric Wong <e@80x24.org>
To: kcar-public@bogomips.org
Subject: [PATCH 1/5] gemspec: use SPDX compatible terms for the license(s)
Date: Fri, 3 Mar 2017 20:53:03 +0000 [thread overview]
Message-ID: <20170303205307.2275-2-e@80x24.org> (raw)
In-Reply-To: <20170303205307.2275-1-e@80x24.org>
This should make things less confusing for automated license
checkers. Disclaimer: I don't like or even understand the
original Ruby license, but only maintain it out of respect for
the original Mongrel license.
---
kcar.gemspec | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/kcar.gemspec b/kcar.gemspec
index 6283992..3d8d39d 100644
--- a/kcar.gemspec
+++ b/kcar.gemspec
@@ -19,5 +19,11 @@ Gem::Specification.new do |s|
s.add_development_dependency('olddoc', '~> 1.0')
s.add_development_dependency('test-unit', '~> 3.0')
- s.licenses = %w(GPLv2+ Ruby)
+ # Note: To avoid ambiguity, we intentionally avoid the SPDX-compatible
+ # 'Ruby' for the Ruby 1.8 license. This is because Ruby 1.9.3 switched
+ # to BSD-2-Clause, but we inherited our license from Mongrel when
+ # Ruby was at 1.8. We cannot automatically switch licenses when Ruby
+ # changes; so we maintain the Ruby 1.8 license (not 1.9.3+) along
+ # with GPL-2.0+
+ s.licenses = %w(GPL-2.0+ Nonstandard)
end
--
EW
next prev parent reply other threads:[~2017-03-03 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 20:53 [PATCH 0/5] miscellaneous updates Eric Wong
2017-03-03 20:53 ` Eric Wong [this message]
2017-03-03 20:53 ` [PATCH 2/5] archive/slrnpull.conf: add a note explaining the purpose Eric Wong
2017-03-03 20:53 ` [PATCH 3/5] drop rb_str_set_len compatibility replacement Eric Wong
2017-03-03 20:53 ` [PATCH 4/5] remove rb_str_modify workaround Eric Wong
2017-03-03 20:53 ` [PATCH 5/5] TypedData C-API conversion Eric Wong
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
List information: https://yhbt.net/kcar/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170303205307.2275-2-e@80x24.org \
--to=e@80x24.org \
--cc=kcar-public@bogomips.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/kcar.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).