1 |
On Wed, 2006-11-22 at 10:57 +0100, Marijn Schouten wrote: |
2 |
> Duncan wrote: |
3 |
> > Marien Zwart <marienz@g.o> posted |
4 |
> > 20061121183634.GA6948@×××××××.localdomain, excerpted below, on Tue, 21 |
5 |
> > Nov 2006 19:36:35 +0100: |
6 |
> > |
7 |
> >> Since check_license was (I assume) originally added because it was |
8 |
> >> required for certain (mostly games) ebuilds: is the possibility to accept |
9 |
> >> the license by putting a wildcard or group in ACCEPT_LICENSE "compatible" |
10 |
> >> with those licenses? If it is not this would need some more thought: it |
11 |
> >> would be quite confusing if certain licenses did not follow the same |
12 |
> >> "rules" for groups and wildcards as other licenses, or if portage followed |
13 |
> >> different rules at resolve time than check_license in eutils does. |
14 |
> > |
15 |
> > As I've read the GLEP (as proposed for update), you are missing something |
16 |
> > here. The package manager's treatment of ACCEPT_LICENSE will simply be |
17 |
> > masking/unmasking of the appropriate ebuilds. It won't change whether |
18 |
> > interactive license agreement is required or not, simply whether such a |
19 |
> > package is masked or not. Thus, accepting an interactive license will be |
20 |
> > a two-stage process -- (1) unmask it by setting ACCEPT_LICENCE |
21 |
> > appropriately so the ebuild can even be considered for merging, (2) emerge |
22 |
> > the package and hit the interactive merge section, actually accepting the |
23 |
> > license there. |
24 |
> > |
25 |
> > Setting ACCEPT_LICENSE therefore won't actually accept it. It'll simply |
26 |
> > tell the package manager whether it can consider certain packages or not. |
27 |
> > Once the package manager can do so, it can go ahead and actually display |
28 |
> > the license for agreement if the package is actually merged. |
29 |
> > |
30 |
> |
31 |
> Maybe it should be called ACCEPTABLE_LICENSES. |
32 |
|
33 |
How about ACCEPTABLE_KEYWORDS, too? *roll eyes* |
34 |
|
35 |
Seriously folks, the variable is to indicate that you accept a license. |
36 |
Hence, ACCEPT_LICENSE, just like how ACCEPT_KEYWORDS means you accept |
37 |
that KEYWORD. |
38 |
|
39 |
-- |
40 |
Chris Gianelloni |
41 |
Release Engineering Strategic Lead |
42 |
Alpha/AMD64/x86 Architecture Teams |
43 |
Games Developer/Council Member/Foundation Trustee |
44 |
Gentoo Foundation |