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: Sun, 09 May 2021 10:33:01 +0200 [thread overview]
Message-ID: <6844f23ac05f0d6aa739a76eecbd9ca183e53051.camel@telenet.be> (raw)
In-Reply-To: <7e605fcdba4ac830ab73719dcda902a2a39ad93a.camel@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Leo Prikler schreef op zo 09-05-2021 om 01:04 [+0200]:
> > and insteads prefers something with basically no licenses.
I meant to write
‘and instead prefers something with basically no restrictions at all’.
here.
> > I would find it interesting to know if some ‘legal people’ have
> > worked out this situation.
> Which ones? The ones who tell you "you must form a bill of materials"
> or the ones who tell you "just provide the source"? :)
The ones that don't simply tell ‘do this’ or ‘do that’ but explain their
reasoning carefully. E.g., I recently came across
<https://web.archive.org/web/20140427195428/http://rechten.eldoc.ub.rug.nl/FILES/root/Algemeen/Recht2/2007/GPLauteursrechtelijk/GPL.pdf>
which I'm now reading.
‘Just provide the source’ is a bit simplistic anyways. If APP derives
from GPL-LIB, then you can't release APP as $PROPIETARY even if you
provide the source code of APP and GPL-LIB.
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-09 8:34 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
2021-05-08 23:04 ` Leo Prikler
2021-05-09 8:33 ` Maxime Devos [this message]
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=6844f23ac05f0d6aa739a76eecbd9ca183e53051.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).