1 |
On Tue, 2006-11-21 at 19:36 +0100, Marien Zwart wrote: |
2 |
> Will portage export ACCEPT_LICENSE with the groups, wildcards and |
3 |
> package.license entries expanded? If I try to emerge something with a |
4 |
> license not in NON-MUST-HAVE-READ, then accept the license by setting |
5 |
> it to "*" or including a group including this license, then merge the |
6 |
> ebuild, I would expect "check_license" to treat the license as |
7 |
> "accepted". |
8 |
|
9 |
Well, we specifically didn't allow a "*" setting because of this. |
10 |
|
11 |
While check_license won't accept groups (simply because there was never |
12 |
any final outcome on them), portage will. I can't think of many groups |
13 |
that would be viable here, though. |
14 |
|
15 |
> Since check_license was (I assume) originally added because it was |
16 |
> required for certain (mostly games) ebuilds: is the possibility to |
17 |
> accept the license by putting a wildcard or group in ACCEPT_LICENSE |
18 |
> "compatible" with those licenses? If it is not this would need some |
19 |
> more thought: it would be quite confusing if certain licenses did not |
20 |
> follow the same "rules" for groups and wildcards as other licenses, or |
21 |
> if portage followed different rules at resolve time than check_license |
22 |
> in eutils does. |
23 |
|
24 |
There's no support for a wildcard. This is the reason that |
25 |
NON-INTERACTIVE was created. It essentially *is* the wildcard. By |
26 |
defining it explicitly, we've let users know that they can expect |
27 |
licenses not included to behave differently. |
28 |
|
29 |
Perhaps we should make it simple and specify that no interactive license |
30 |
should belong to a group? That would mean that since we don't include |
31 |
it in a group, it won't be part of the "wildcard" NON-INTERACTIVE (or |
32 |
whatever it's called) which would make the behavior the same as we |
33 |
currently have with check_license, since I think adding group support to |
34 |
check_license would be pointless when we're trying to replace it. |
35 |
|
36 |
-- |
37 |
Chris Gianelloni |
38 |
Release Engineering Strategic Lead |
39 |
Alpha/AMD64/x86 Architecture Teams |
40 |
Games Developer/Council Member/Foundation Trustee |
41 |
Gentoo Foundation |