From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: new global USE flag "srcdist"
Date: Thu, 2 Jan 2014 12:35:26 +0100 [thread overview]
Message-ID: <21189.20222.531360.693783@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <CAGfcS_n5pW8gb3DumvVFk6RvJdyhH71V9_byR22ZrOPNBmwEbw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
>>>>> On Wed, 1 Jan 2014, Rich Freeman wrote:
> On Wed, Jan 1, 2014 at 8:51 PM, Michael Orlitzky <mjo@gentoo.org>
> wrote:
>> I think a better solution here, since these files are *installed*,
>> is to introduce a new local flag (e.g. unfreeblobs) for the kernel
>> that would append to LICENSE by the mechanism described below.
> Well, sure, any USE flag that controls the installation of the blobs
> should append the appropriate string to LICENSE. However, that is a
> separate (and also important) issue.
The kernel does this already. kernel-2.eclass (basically) assigns:
LICENSE="GPL-2 !deblob? ( freedist )"
So with USE=deblob you get GPL-2 because only GPL-2 files will be
installed on your system. (Of course, "freedist" is only a crude
approximation of the actual firmware licenses. But this is a separate
issue, see https://bugs.gentoo.org/show_bug.cgi?id=318841#c9).
> Has anybody tested whether ACCEPT_LICENSE handles USE conditionals
> correctly? If it is in PMS and it doesn't than that would be a
> Portage bug, but we should probably be aware of what it does before
> setting it all over the tree.
Ack. It is specified in GLEP 23 and PMS, and Portage does handle it
correctly.
Ulrich
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-01-02 11:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 22:28 [gentoo-dev] RFC: new global USE flag "srcdist" Ulrich Mueller
2014-01-02 1:21 ` Rick "Zero_Chaos" Farina
2014-01-02 1:51 ` Michael Orlitzky
2014-01-02 2:10 ` Rich Freeman
2014-01-02 2:19 ` Michael Orlitzky
2014-01-02 2:38 ` Rich Freeman
2014-01-02 2:50 ` Michael Orlitzky
2014-01-02 2:57 ` Rich Freeman
2014-01-02 12:54 ` Ulrich Mueller
2014-01-02 15:25 ` Michael Orlitzky
2014-01-02 16:24 ` Rich Freeman
2014-01-02 11:35 ` Ulrich Mueller [this message]
2014-01-02 2:13 ` Rick "Zero_Chaos" Farina
2014-01-02 2:40 ` Michael Orlitzky
2014-01-02 2:43 ` Rick "Zero_Chaos" Farina
2014-01-02 8:56 ` Michał Górny
2014-01-02 12:45 ` Ulrich Mueller
2014-01-02 12:50 ` [gentoo-dev] " Ryan Hill
2014-01-02 12:54 ` Ryan Hill
2014-01-02 13:18 ` Ulrich Mueller
2014-01-02 14:07 ` Kent Fredric
2014-01-02 14:01 ` Kent Fredric
2014-01-02 16:10 ` Ian Stakenvicius
2014-01-02 16:28 ` Luis Ressel
2014-01-02 16:37 ` Kent Fredric
2014-01-02 17:02 ` Luis Ressel
2014-01-03 14:09 ` Kent Fredric
2014-01-02 16:53 ` Ulrich Mueller
2014-01-02 17:02 ` Luis Ressel
2014-01-02 18:17 ` Ulrich Mueller
2014-01-02 18:27 ` Rich Freeman
2014-01-02 18:34 ` Ulrich Mueller
2014-01-02 21:11 ` Ryan Hill
2014-01-02 21:20 ` Rich Freeman
2014-01-02 22:07 ` Ryan Hill
2014-01-02 22:53 ` Ryan Hill
2014-01-02 23:53 ` Ulrich Mueller
2014-01-05 3:00 ` Ryan Hill
2014-01-02 17:13 ` Ian Stakenvicius
2014-01-02 18:25 ` Luis Ressel
2014-01-02 21:24 ` Ryan Hill
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=21189.20222.531360.693783@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@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