From: Arun Isaac <arunisaac@systemreboot.net>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Question about multiple licenses
Date: Mon, 28 Aug 2017 22:55:34 +0530 [thread overview]
Message-ID: <f0dbb5fc.AEEAPdjxcb8AAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZpFIv@mailjet.com> (raw)
In-Reply-To: <87mv6kj7i7.fsf@gmail.com>
Alex Vong writes:
> Based on the above general argument, I think we should list all the
> licenses instead of just GPLv2+ since it would be inaccurate to say that
> the whole program is under just GPLv2+.
Listing all the licenses does seem like the safest thing to do.
> Also, in this particular case, since ASL2.0 is incompatible with GPLv2,
> we actually need to take advantage of the "or later" clause, and
> "upgrades" it to "GPLv3+".
Is there any Guix package where we have actually done such a license
upgrade?
> Listing the license as GPLv2+ would confuse the user that GPLv2 covers
> the program, but in fact it is "effectively" GPLv3.
>
> Of course, I am not a lawyer. I only get the info from reading the
> web. So I could be saying nonsense...
>
> [0]: https://www.gnu.org/licenses/gpl-faq.en.html#AllCompatibility
next prev parent reply other threads:[~2017-08-28 17:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 7:40 Question about multiple licenses Arun Isaac
2017-08-28 10:45 ` Alex Vong
2017-08-28 17:25 ` Arun Isaac [this message]
2017-08-28 17:29 ` Efraim Flashner
2017-08-29 6:30 ` Arun Isaac
2017-09-01 11:43 ` Dave Love
2017-09-02 16:54 ` Alex Vong
2017-09-07 16:21 ` Dave Love
2017-09-03 11:45 ` Arun Isaac
2017-09-04 14:57 ` Ludovic Courtès
2017-09-07 16:20 ` Dave Love
2017-09-10 20:54 ` Ludovic Courtès
2017-09-11 11:29 ` Alex Vong
2017-09-11 12:45 ` Andy Wingo
2017-09-12 22:15 ` Dave Love
2017-09-12 22:13 ` Dave Love
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=f0dbb5fc.AEEAPdjxcb8AAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZpFIv@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
/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.