| 1 |
Duncan wrote: |
| 2 |
> Marien Zwart <marienz@g.o> posted |
| 3 |
> 20061121183634.GA6948@×××××××.localdomain, excerpted below, on Tue, 21 |
| 4 |
> Nov 2006 19:36:35 +0100: |
| 5 |
> |
| 6 |
>> Since check_license was (I assume) originally added because it was |
| 7 |
>> required for certain (mostly games) ebuilds: is the possibility to accept |
| 8 |
>> the license by putting a wildcard or group in ACCEPT_LICENSE "compatible" |
| 9 |
>> with those licenses? If it is not this would need some more thought: it |
| 10 |
>> would be quite confusing if certain licenses did not follow the same |
| 11 |
>> "rules" for groups and wildcards as other licenses, or if portage followed |
| 12 |
>> different rules at resolve time than check_license in eutils does. |
| 13 |
> |
| 14 |
> As I've read the GLEP (as proposed for update), you are missing something |
| 15 |
> here. The package manager's treatment of ACCEPT_LICENSE will simply be |
| 16 |
> masking/unmasking of the appropriate ebuilds. It won't change whether |
| 17 |
> interactive license agreement is required or not, simply whether such a |
| 18 |
> package is masked or not. Thus, accepting an interactive license will be |
| 19 |
> a two-stage process -- (1) unmask it by setting ACCEPT_LICENCE |
| 20 |
> appropriately so the ebuild can even be considered for merging, (2) emerge |
| 21 |
> the package and hit the interactive merge section, actually accepting the |
| 22 |
> license there. |
| 23 |
> |
| 24 |
> Setting ACCEPT_LICENSE therefore won't actually accept it. It'll simply |
| 25 |
> tell the package manager whether it can consider certain packages or not. |
| 26 |
> Once the package manager can do so, it can go ahead and actually display |
| 27 |
> the license for agreement if the package is actually merged. |
| 28 |
> |
| 29 |
|
| 30 |
Maybe it should be called ACCEPTABLE_LICENSES. |
| 31 |
|
| 32 |
Marijn |
| 33 |
-- |
| 34 |
gentoo-dev@g.o mailing list |
Archives