| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 01/01/2014 05:28 PM, Ulrich Mueller wrote: |
| 5 |
> Hi, According to GLEP 23 [1], the LICENSE variable regulates the |
| 6 |
> software that is installed on a system. There is however some |
| 7 |
> ambiguity in this: should it cover the actual files installed on |
| 8 |
> the system, or everything that is included in the package's |
| 9 |
> tarball? This question was asked several times in the past and |
| 10 |
> arose in bug 492424 [2] again. |
| 11 |
> |
| 12 |
> I've always preferred the first interpretation, because the second |
| 13 |
> one would inevitably require us to repack many tarballs, in order |
| 14 |
> to keep their license in @FREE. This would for example include the |
| 15 |
> Linux kernel, where we could no longer use deblobbing, but would |
| 16 |
> have to provide our own tarball with firmware blobs removed. Not |
| 17 |
> sure if users would be happy if we wouldn't install from pristine |
| 18 |
> sources any more. We also have mirror and fetch restrictions which |
| 19 |
> allow us to control what tarballs we distribute, independent of the |
| 20 |
> LICENSE variable. |
| 21 |
> |
| 22 |
> Nevertheless, I also see the point for covering the distfiles |
| 23 |
> contents. |
| 24 |
> |
| 25 |
> Within existing EAPIs we have only one LICENSE variable available. |
| 26 |
> (Extending it would be possible in future EAPIs, but we would end |
| 27 |
> up with a very long transition period.) USE conditional syntax is |
| 28 |
> allowed in LICENSE, though. So I wonder if this couldn't be used |
| 29 |
> for the intended purpose. For example, for specifying licenses of |
| 30 |
> distfiles: |
| 31 |
> |
| 32 |
> LICENSE="<licenses of installed stuff> srcdist? ( <licenses of |
| 33 |
> unused stuff in distfiles> )" |
| 34 |
> |
| 35 |
> This idea was discussed within the licenses team, and the overall |
| 36 |
> reaction was positive. |
| 37 |
> |
| 38 |
> What do you think? |
| 39 |
|
| 40 |
Assuming this flag is not set by default on user systems (since they |
| 41 |
obviously are not all distributing sources) I think it's a very |
| 42 |
positive change. I myself would need to have this flag set on my |
| 43 |
build box and it would help me better adhere to the correct licensing |
| 44 |
terms. |
| 45 |
|
| 46 |
- -Zero |
| 47 |
> |
| 48 |
> Ulrich |
| 49 |
> |
| 50 |
> [1] http://www.gentoo.org/proj/en/glep/glep-0023.html [2] |
| 51 |
> https://bugs.gentoo.org/show_bug.cgi?id=492424#c3 |
| 52 |
> |
| 53 |
|
| 54 |
-----BEGIN PGP SIGNATURE----- |
| 55 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 56 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 57 |
|
| 58 |
iQIcBAEBAgAGBQJSxL8cAAoJEKXdFCfdEflK4bQQAKwJmkeDgm3IBcX06QqcDmJ+ |
| 59 |
QqYyE+SLJdJw2Fs9iXExEDa+nc9/6QOZkE1E6AA4wji/jKHDpp7ddnXCVfgNALaS |
| 60 |
KaAlsG+eiJk27C/sfpyT+Nmvd+FPzLcm9cNp8YjOn50BlDfVFUxoE5M3woJiIn/m |
| 61 |
gRbwHZhNVWYnqzHjOwiEhs3mUC6quu9N3c3QPY2k0lKspGW+3yqEqy8wZng9Wli6 |
| 62 |
8nMa1DXg92fk9gcmgpHAYTl0+gBtvv0LVa70fYu5Y+aGJAQEUclaMAlSi0ES4DYi |
| 63 |
7YpEjB2HJOWXFH30DJdhv2E4v5MTHzARgjCGHv6jXvHZfIoS7PbDIbQ2IBpkOpSP |
| 64 |
kyOF2Aj/bWoIvFKzMGPWcDzwQwnfvJ/M615NTgGMZL/Iv04Pdki8W2qTvxsH17m3 |
| 65 |
NvEtdoMrtyT1gvJaLg8/Vsx2EaBYp47iwK81vPHgqQ7TsypO2v5G70Nqk6ogARgF |
| 66 |
gqp524/LUca/mfhKp6LlWT9TXvu2QziE24QYtHQ0mlWer9+KBKX+++dcDyXmF+ww |
| 67 |
KAiz9wsHmMdXsCb5/C2xA3RQk+4lePlFJiYeYs4Ix6/CgdW35w+BjtfAiWNz5rpy |
| 68 |
M5IRAtKQO/VJQlLjfERDfyC2hdSPAqoW/wrmAZ15VqoPnsNabrp8O3fO0+j5kEWq |
| 69 |
WZS6YVfKSghARUAzyP4g |
| 70 |
=7nB6 |
| 71 |
-----END PGP SIGNATURE----- |
Archives