1 |
On Thu, Oct 26, 2006 at 07:02:36PM +0200, Marius Mauch wrote: |
2 |
> Ok, as there is currently a lot of work going on for GLEP 23 |
3 |
> (licese based visibility filtering aka ACCEPT_LICENSE) the topic of |
4 |
> license groups came up, in particular the way how they should be |
5 |
> (technically) defined. |
6 |
> |
7 |
> The simplest way is a line based format |
8 |
> <groupname> <license1> ... <licenseN> |
9 |
> however this doesn't allow for any addition of metadata (for example |
10 |
> descriptions to explain the purpose of a group), these (if wanted) would |
11 |
> have to be defined in another file. |
12 |
|
13 |
A description could be provided in the same file, by allowing comments. |
14 |
|
15 |
> The alternative would be to use a |
16 |
> more complex file format, for example so called ini-style |
17 |
> |
18 |
> [groupname] |
19 |
> licenses=license1 license2 ... licenseN |
20 |
> description=Sample license group |
21 |
> constains_stupid_licenses=1 |
22 |
|
23 |
Something like contains_stupid_licenses (even in an objective form) |
24 |
could be handled differently: a STUPID_LICENSES group, so that |
25 |
ACCEPT_LICENSE can contain "@GROUP1 @GROUP2 -@STUPID_LICENSES". Do you |
26 |
have an example of metadata other than the description that cannot be |
27 |
dealt with another way? |
28 |
-- |
29 |
gentoo-dev@g.o mailing list |