From: Saku Laesvuori <saku@laesvuori.fi>
To: Parnikkapore <poomklao@yahoo.com>
Cc: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
help-guix@gnu.org
Subject: Re: Can Guix channels be non-GPL?
Date: Tue, 13 Jun 2023 16:56:06 +0300 [thread overview]
Message-ID: <20230613135606.oumh2nht4kfolhig@X-kone> (raw)
In-Reply-To: <87352vzm2d.fsf@pelzflorian.de>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
> One view is that GPL does not propagate, because the Guile language does
> not link.
This would be a very dangerous interpretation and clearly go against the
spirit of the GPL: any proprietary software could use any GPL software
if they were written in a language that doesn't link. There is a lot of
python code, for example, under the GPL and it would have no protection
against being used in proprietary programs.
> If Guix’ GPL would propagate, then the GPL2 of libgit2 would propagate
> to Guix.
Libgit2 defines an exception that it may be linked against programs
under any license, and I would consider FFI or whatever Guile uses to
interact with the compiled libgit2 library to qualify as linking.
I feel like Guix' GPL would propagate, but you could ask
licensing@fsf.org what they think about it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-13 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <793f8796901ec5477972c805557bd66267af3310.camel.ref@yahoo.com>
2023-06-12 12:13 ` Can Guix channels be non-GPL? Parnikkapore
2023-06-13 10:35 ` pelzflorian (Florian Pelz)
2023-06-13 13:56 ` Saku Laesvuori [this message]
2023-06-13 15:45 ` Dr. Arne Babenhauserheide
2023-06-13 16:08 ` pelzflorian (Florian Pelz)
2023-06-13 18:39 ` pelzflorian (Florian Pelz)
2023-06-13 18:52 ` Dr. Arne Babenhauserheide
2023-06-14 7:08 ` pelzflorian (Florian Pelz)
2023-06-14 19:51 ` david larsson
2023-06-15 13:45 ` Maxim Cournoyer
2023-06-16 15:09 ` Parnikkapore
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230613135606.oumh2nht4kfolhig@X-kone \
--to=saku@laesvuori.fi \
--cc=help-guix@gnu.org \
--cc=pelzflorian@pelzflorian.de \
--cc=poomklao@yahoo.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).