From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: What should the default acceptable licenses be?
Date: Wed, 13 Feb 2019 10:34:51 +0100 [thread overview]
Message-ID: <c0f97e2c-e237-8280-a5f6-a9b0eaa69d59@gentoo.org> (raw)
In-Reply-To: <CAAr7Pr-Hne5hr3Psa1s7tdPY872fWaL5h=8kidqECjx7iU7MsA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1796 bytes --]
On 2019-02-12 20:40, Alec Warner wrote:
> This is why I continue to advocate for a deliberate choice based on
> the social contract ("Gentoo is and will remain Free and thus the
> default should be "-* @FREE" rather than some kind of objective
> choice based on 'consequences'; which I think just muddle the point.
Sorry, I don't get this. You understand that a change from
> ACCEPT_LICENSE="* -@EULA" (active today)
to
> ACCEPT_LICENSE="-* @FREE"
is the same like
> ACCEPT_LICENSE="@FREE"
Isn't it ("-*" isn't needed; at the moment we say "don't prompt for _any
license_ except licenses from @EUAL group")?
And I also don't understand people discussing consequences:
1) There's no hard block.
2) Existing systems won't break because PM will prompt to accept any
license of installed packages not yet accepted. Even in case you will
reject that prompt, your existing system won't break (you won't get new
updates for those packages, that's all).
3) New users will have to learn about ACCEPT_LICENSE earlier, that's all.
4) There's also no plan to force projects like releng to stick to
ACCEPT_LICENSE default. If any project wants to use package X which
requires license Y they are free to do so (of course you have to comply
with law, only content which we are allowed to redistribute...).
5) This change will basically only affect stage3. And ulm already did an
audit of stage3 and aside kernel sources (due to outdated eclass) all
currently included packages are only using licenses from @FREE group. So
if you want to, you could say, we are only adjust ACCEPT_LICENSE to
licenses we are actually using in our stage3.
--
Regards,
Thomas Deutschmann / Gentoo Linux Developer
C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-02-13 9:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 21:04 [gentoo-project] What should the default acceptable licenses be? Kristian Fiskerstrand
2019-01-26 21:32 ` [gentoo-project] " Chí-Thanh Christopher Nguyễn
2019-01-27 9:47 ` Ulrich Mueller
2019-01-26 21:45 ` Thomas Deutschmann
2019-01-26 22:12 ` [gentoo-project] " Michał Górny
2019-01-26 22:51 ` Rich Freeman
2019-01-27 1:25 ` Alec Warner
2019-01-28 22:27 ` Matt Turner
2019-01-29 16:54 ` Thomas Deutschmann
2019-01-29 17:28 ` Brian Evans
2019-02-05 20:03 ` Roy Bamford
2019-01-29 17:53 ` Alec Warner
2019-01-29 18:27 ` Rich Freeman
2019-01-29 18:41 ` Kristian Fiskerstrand
2019-01-29 18:56 ` Kristian Fiskerstrand
2019-01-30 0:12 ` Thomas Deutschmann
2019-01-30 0:35 ` Alec Warner
2019-01-29 17:53 ` Rich Freeman
2019-01-31 16:53 ` Matt Turner
2019-02-05 23:47 ` [gentoo-project] " Kristian Fiskerstrand
2019-02-12 19:40 ` Alec Warner
2019-02-13 9:34 ` Thomas Deutschmann [this message]
2019-02-13 9:50 ` Kristian Fiskerstrand
2019-02-13 10:44 ` Ulrich Mueller
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=c0f97e2c-e237-8280-a5f6-a9b0eaa69d59@gentoo.org \
--to=whissi@gentoo.org \
--cc=gentoo-project@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox