all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: pukkamustard <pukkamustard@posteo.net>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 57055@debbugs.gnu.org
Subject: [bug#57055] [PATCH 2/2] gnu: Add guile-srfi-146.
Date: Fri, 19 Aug 2022 13:41:10 +0000	[thread overview]
Message-ID: <86sflse40m.fsf@posteo.net> (raw)
In-Reply-To: <8aafcdc2-cb1a-6d38-1832-52fd53fc85ec@telenet.be>


Sorry for the delayed response. I seem to have missed this mail.

Maxime Devos <maximedevos@telenet.be> writes:

> [[PGP Signed Part:Undecided]]
> On 08-08-2022 14:43, pukkamustard wrote:
>
>  +    (license license:lgpl3+)))
>
> There are also some (ISC?) bits on
> <https://inqlab.net/git/guile-srfi-146.git/tree/srfi/srfi-146.scm>.
>
> Yes, the sample SRFI implementation is licensed under ISC. Afaiu,
> there's no problem in relicensing this as LGPL-3.0-or-later. I think a
> lot of the guile-srfi-* libraries do this.
>
> I have looked at license text, and it states that it allows 'sublicensing', but it doesn't say anything about relicensing (except maybe for
> the "deal in the Software without restriction"?).
>
> As such, I think it would be safer to just include license:isc in the list.

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.

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. In the Guix package definition for
Guile only license:lgpl3+ is listed (and not license:isc).

Cheers,
pukkamustard




  reply	other threads:[~2022-08-19 13:51 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 [this message]
2022-08-19 20:34             ` Maxime Devos
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=86sflse40m.fsf@posteo.net \
    --to=pukkamustard@posteo.net \
    --cc=57055@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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.