From: Maxime Devos <maximedevos@telenet.be>
To: Leo Prikler <leo.prikler@student.tugraz.at>,
Chris Marusich <cmmarusich@gmail.com>,
Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: The purpose of the "license" list of a Guix package (Was: Re: Jam: which licence is this?)
Date: Sat, 08 May 2021 22:52:08 +0200 [thread overview]
Message-ID: <9b059ccb9cc50e27329824f88d9d049072d30f23.camel@telenet.be> (raw)
In-Reply-To: <ac943dc1c460383bbeaddc6ce318e658636c07bc.camel@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
Leo Prikler schreef op za 08-05-2021 om 12:16 [+0200]:
> [... something about dependencies and copyleft ...]
> [...]
> However, compliance is not *that* simple. If you're dealing with
> copyleft, providing the source is not enough, you also need to license
> your own work under that copyleft license, e.g. the GPL. [...]
Just checking if our understanding is the same, as I have seen a discussion
on IRC where people the situation described below was _not_ legally acceptable.
Suppose we have a GPLv3+ library, say guile-jwt.
Suppose there is a (group of) developer(s) writing an application using
guile-jwt. Let's call the application APP, and the developer(s) DEV.
A hypothetical situation:
* Suppose DEV is not very fond of licensing APP under a copyleft license,
and insteads prefers something with basically no licenses.
* DEV wants to choose, say, license:expat.
* license:expat is not license:gpl3
* Would this be a problem? I would think not. While APP used guile-jwt,
it doesn't include or modify its source code.
So I would think DEV
must still respect GPL for the combination (e.g., if DEV provides binaries
for APP, they must include source code for guile-jwt *and* APP),
and theoretically someone may fork APP to replace guile-jwt with
a hypothetical guile-jwt/expat, and at that point the GPL doesn't
apply anymore to the combination APP-with-guile-jwt/expat.
<insert standard IANAL disclaimer here>
I would find it interesting to know if some ‘legal people’ have worked out
this situation.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-05-08 20:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 6:15 Jam: which licence is this? Jack Hill
2021-04-25 7:16 ` Ricardo Wurmus
2021-04-25 17:25 ` Mark H Weaver
2021-04-25 17:35 ` Leo Famulari
2021-04-25 20:37 ` Mark H Weaver
2021-04-26 16:24 ` Leo Famulari
2021-05-02 4:53 ` Mark H Weaver
2021-05-02 15:20 ` Leo Famulari
2021-05-07 18:31 ` The purpose of the "license" list of a Guix package (Was: Re: Jam: which licence is this?) Chris Marusich
2021-05-07 19:23 ` The purpose of the "license" list of a Guix package Chris Marusich
2021-05-08 10:16 ` The purpose of the "license" list of a Guix package (Was: Re: Jam: which licence is this?) Leo Prikler
2021-05-08 11:17 ` Ricardo Wurmus
2021-05-08 11:22 ` Leo Prikler
2021-05-08 20:52 ` Maxime Devos [this message]
2021-05-08 23:04 ` Leo Prikler
2021-05-09 8:33 ` Maxime Devos
2021-05-02 21:12 ` Jam: which licence is this? Ludovic Courtès
2021-04-25 17:42 ` Mark H Weaver
2021-04-28 13:20 ` Maxim Cournoyer
2021-04-25 20:23 ` Vagrant Cascadian
2021-04-25 20:49 ` Ricardo Wurmus
2021-04-25 20:53 ` Jack Hill
2021-04-25 21:04 ` Jack Hill
2021-04-26 14:36 ` Jack Hill
2021-05-02 5:02 ` Mark H Weaver
2021-04-25 21:41 ` Vagrant Cascadian
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=9b059ccb9cc50e27329824f88d9d049072d30f23.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=leo@famulari.name \
/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://git.savannah.gnu.org/cgit/guix.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).