public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: new global USE flag "srcdist"
Date: Wed, 01 Jan 2014 21:13:46 -0500	[thread overview]
Message-ID: <52C4CB5A.4080108@gentoo.org> (raw)
In-Reply-To: <52C4C610.1000303@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/01/2014 08:51 PM, Michael Orlitzky wrote:
> On 01/01/2014 05:28 PM, Ulrich Mueller wrote:
>> Hi,
>> According to GLEP 23 [1], the LICENSE variable regulates the software
>> that is installed on a system. There is however some ambiguity in
>> this: should it cover the actual files installed on the system, or
>> everything that is included in the package's tarball? This question
>> was asked several times in the past and arose in bug 492424 [2] again.
> 
> Why do I as a user care about the license of a package? I want packages
> to be in @FREE in case I need to modify (and redistribute) them. But I
> only need to modify the parts that I use.
> 
> If an otherwise-GPL package pulls in the latest Justin Bieber CD with
> USE=badtaste, that's not really an issue for me, because I'm not using
> it. I'm happy to install the rest of the package with the USE flag
> unset. The CD might as well be a separate package with a different
> license as far as I'm concerned.
> 
> In essence, I don't want to *use* code that isn't @FREE. This includes
> the installed files, of course, but also the build system (that I use
> temporarily). We could generalize this to "any file accessed during
> emerge" to be on the safe side. That ensures that if I need to modify
> (and redistribute) any part of the software that I use, I can.
> 
> What use case is there for having the LICENSE apply to anything else?

Some of us do redistribute the entire source package, so it does matter.
 If it doesn't matter to you as a user then you can always leave it
unset and you remain completely oblivious to the change.

- -Zero

> 
> 
>> I've always preferred the first interpretation, because the second one
>> would inevitably require us to repack many tarballs, in order to keep
>> their license in @FREE. This would for example include the Linux
>> kernel, where we could no longer use deblobbing, but would have to
>> provide our own tarball with firmware blobs removed. Not sure if users
>> would be happy if we wouldn't install from pristine sources any more.
>> We also have mirror and fetch restrictions which allow us to control
>> what tarballs we distribute, independent of the LICENSE variable.
> 
> 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.
> 
> 
>> Nevertheless, I also see the point for covering the distfiles
>> contents.
>>
>> Within existing EAPIs we have only one LICENSE variable available.
>> (Extending it would be possible in future EAPIs, but we would end up
>> with a very long transition period.) USE conditional syntax is allowed
>> in LICENSE, though. So I wonder if this couldn't be used for the
>> intended purpose. For example, for specifying licenses of distfiles:
>>
>> 	LICENSE="<licenses of installed stuff>
>> 		srcdist? ( <licenses of unused stuff in distfiles> )"
>>
>> This idea was discussed within the licenses team, and the overall
>> reaction was positive.
>>
>> What do you think?
>>
>> Ulrich
>>
>> [1] http://www.gentoo.org/proj/en/glep/glep-0023.html
>> [2] https://bugs.gentoo.org/show_bug.cgi?id=492424#c3
>>
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSxMtZAAoJEKXdFCfdEflK4uIP/RAl9JWej7SInRWRkMRFTiWe
SAGcvNUm7qbVKCPYWDKp82+3fN6wEXSWLRcB2nCS8jZy8adzEOF0Oqvym17J3sEI
wfiB3lI5VNCkx7lX0wJiYIbCmKVR6PgwTdeBGcDIzdgU2TPygXLADbBu7n+54f7U
XAWcKPQRcuAzBFxCzuL1yWQzBuovhTU9HMelPaYPkXUGvi+LWlfmDBXe2mG1gfD+
U8sNOyHjwuidR6slr9RjxFAkH5ItVzeRBMiE92kHurZpm06sVaqezj0Oj1PovgqS
ap/S/ncTQa7BrhmdzEIAqaLko/bpxJkjdWvEhj+MPQ453Et5+RvztE1h5KUdXrFj
QU/oKS2Pmh75cROlipSfN628cdBDYQ8x/eB8XIZDPKd4uc7i43tpYf8njbNNrLlG
jdioBnXEowJ+UQ/5vDM1s8ev3FToIfZRU1nFxREdJEYXx4qVhrZ/8yBlv7RWGcbs
IsCJEtbrUFAcNBMowQ6eN2SfWGrx8lpB+Qoh8WhsUR7XMuyBQYB0jCOOfeV8qDWd
kZn/t2+0daTxo70KRTLiVutHbqAaBjG1BF0iwZhS5YGmDufc2hm0fKgu7tzZb/HU
Q0jA9hgWLvAj4dqek7qp1j21af993tZadIR1gjU0WgY0HiEHFYmY1xqy8GF09ZgX
39Jvtx4tu9UEpgk0ERYA
=aSba
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2014-01-02  2:13 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
2014-01-02  2:13   ` Rick "Zero_Chaos" Farina [this message]
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=52C4CB5A.4080108@gentoo.org \
    --to=zerochaos@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