From: Ulrich Mueller <ulm@gentoo.org>
To: Thomas Deutschmann <whissi@gentoo.org>
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: What should the default acceptable licenses be?
Date: Wed, 13 Feb 2019 11:44:44 +0100 [thread overview]
Message-ID: <w6glg2kx90j.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <c0f97e2c-e237-8280-a5f6-a9b0eaa69d59@gentoo.org> (Thomas Deutschmann's message of "Wed, 13 Feb 2019 10:34:51 +0100")
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
>>>>> On Wed, 13 Feb 2019, Thomas Deutschmann wrote:
> 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")?
It is the same when starting from an empty default. IIUC, Portage
does its lookup in the order make.globals, then make.defaults,
then make.conf, so keeping the "-*" would have the advantage that it
overrides the default of previous Portage versions. Otherwise, I don't
see how "-* @FREE" (rather than "@FREE") could cause any harm.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2019-02-13 10:44 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
2019-02-13 9:50 ` Kristian Fiskerstrand
2019-02-13 10:44 ` Ulrich Mueller [this message]
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=w6glg2kx90j.fsf@kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=whissi@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