| 1 |
On Sat, 2006-11-18 at 13:25 -0800, Brian Harring wrote: |
| 2 |
> > License groups may be negated with the result that all elements of that group |
| 3 |
> > are also negated. |
| 4 |
> |
| 5 |
> Left out that if it's unset, it should default to ACCEPT_LICENSE=* , |
| 6 |
> meaning no license filtering. |
| 7 |
|
| 8 |
Except that it shouldn't. It should be set to @NON-INTERACTIVE, as the |
| 9 |
GLEP says, to match what we currently have with the combination of |
| 10 |
portage+eutils.eclass settings. |
| 11 |
|
| 12 |
Certain packages will *always* require interactive acceptance of the |
| 13 |
license, as they currently do. |
| 14 |
|
| 15 |
> > There should be no change to the user experience without the user |
| 16 |
> > explicitly choosing to do so. This mandates that the |
| 17 |
> > configuration variable be named ``ACCEPT_LICENSE`` as some users may |
| 18 |
> > already have it set due to ebuilds using ``eutil.eclass``'s |
| 19 |
> > implementation. It also mandates that the default ``ACCEPT_LICENSE`` be |
| 20 |
> > set to ``@NON-INTERACTIVE`` in the main gentoo repository as there will |
| 21 |
> > be no internal default in portage. |
| 22 |
> |
| 23 |
> The current default in portage however is that of ACCEPT_LICENSE=*; |
| 24 |
> since portage doesn't yet filter on licenses, and since interactive |
| 25 |
> ebuilds already exist, _that_ is the default. |
| 26 |
|
| 27 |
Not really. |
| 28 |
|
| 29 |
Go look at some of my games ebuilds. While *portage* doesn't do |
| 30 |
anything with the license, the ebuild does, due to licensing |
| 31 |
restrictions. The idea here is to not lose functionality by moving this |
| 32 |
to portage itself. |
| 33 |
|
| 34 |
> Finally, NON-INTERACTIVE shouldn't be a license group; |
| 35 |
> RESTRICT=interactive is the route there; you can have gpl software |
| 36 |
> distributed on cds that must be interactive (feed cds in as |
| 37 |
> requested). |
| 38 |
|
| 39 |
No. Apples and oranges. |
| 40 |
|
| 41 |
Here, INTERACTIVE means that the user must interactively accept the |
| 42 |
license, not that the ebuild is interactive. They're not the same |
| 43 |
thing. |
| 44 |
|
| 45 |
games-fps/enemy-territory requires interactivity *only* for license |
| 46 |
acceptance. It pulls all data from the Internet, just like any other |
| 47 |
ebuild. The only reason it is interactive, at all, it due to the |
| 48 |
license. |
| 49 |
|
| 50 |
-- |
| 51 |
Chris Gianelloni |
| 52 |
Release Engineering Strategic Lead |
| 53 |
Alpha/AMD64/x86 Architecture Teams |
| 54 |
Games Developer/Council Member/Foundation Trustee |
| 55 |
Gentoo Foundation |
Archives