From: Maxime Devos <maximedevos@telenet.be>
To: pukkamustard <pukkamustard@posteo.net>
Cc: 57055@debbugs.gnu.org
Subject: [bug#57055] [PATCH 2/2] gnu: Add guile-srfi-146.
Date: Fri, 19 Aug 2022 22:34:50 +0200 [thread overview]
Message-ID: <c9dc1aa3-0b61-9d14-a3fb-cf36b0b847f2@telenet.be> (raw)
In-Reply-To: <86sflse40m.fsf@posteo.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 1815 bytes --]
On 19-08-2022 15:41, pukkamustard wrote:
> I'm no legal expert, but I think I am free to distribute it only
> under LGPL-3.0-or-later (and not also ISC). And I prefer to do so.
Sure, go ahead and distribute it as LGPL-3.0-or-later, but I don't see
how it follows that license:isc should be removed from the license list.
However, to me it seems inaccurate that you do not have to follow the
ISC by following the LGPL-3.0-or-later instead. The ISC has a line:
> ;; [...] The above copyright notice and this permission notice shall
> be included
> ;; in all copies or substantial portions of the Software. [...]
Even if ISC permits relicensing, I would assume you will still have to
follow that. Otherwise, you could circumvent 'preserve this copyright
notice / preserve authorship information / ...’ requirements by
relicensing it as something very permissive, which seems a loophole to me.
> For prior cases see modules/srfi/srfi-71.scm as distributed with
> Guile. The file contains a SRFI sample implementation with the same ISC
> license header. It seems to be fine to relicense modules distributed
> with Guile as LGPL-3.0-or-later.
I am not following, how is this relicensing?
> In the Guix package definition for Guile only license:lgpl3+ is listed (and not license:isc).
Right, I would add license:isc with an appropriate comment to the list
in the Guile package definition, looks like the license information for
that package is incomplete.
[...]
More generally, I don't see a need for computing an 'effective license'
(*) of the licenses of the individual files, given the lack of legal
experts here and as 'licenses' accepts a list, not only a single item.
(*) things like 'isc or expat + lgplN-or-later -> lgplN-or-later'.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-08-19 20:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 8:32 [bug#57055] [PATCH 0/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-08 8:36 ` [bug#57055] [PATCH 1/2] gnu: Add guile-srfi-128 pukkamustard
2022-08-08 8:36 ` [bug#57055] [PATCH 2/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-08 9:30 ` Maxime Devos
2022-08-08 12:43 ` pukkamustard
2022-08-08 13:12 ` ( via Guix-patches via
2022-08-08 13:47 ` pukkamustard
2022-08-08 18:22 ` Maxime Devos
2022-08-19 13:41 ` pukkamustard
2022-08-19 20:34 ` Maxime Devos [this message]
2022-08-29 8:48 ` pukkamustard
2022-08-08 19:04 ` Maxime Devos
2022-08-09 9:24 ` pukkamustard
2022-08-09 9:30 ` [bug#57055] [PATCH v2 1/2] gnu: Add guile-srfi-128 pukkamustard
2022-08-09 9:30 ` [bug#57055] [PATCH v2 2/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-29 8:55 ` [bug#57055] [PATCH v3 1/2] gnu: Add guile-srfi-128 pukkamustard
2022-08-29 8:56 ` [bug#57055] [PATCH v3 2/2] gnu: Add guile-srfi-146 pukkamustard
2022-08-31 21:14 ` bug#57055: [PATCH 0/2] " Ludovic Courtès
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=c9dc1aa3-0b61-9d14-a3fb-cf36b0b847f2@telenet.be \
--to=maximedevos@telenet.be \
--cc=57055@debbugs.gnu.org \
--cc=pukkamustard@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.