1 |
Marius Mauch wrote: |
2 |
> On Thu, 05 Jun 2008 15:42:24 -0400 |
3 |
> Doug Goldstein <cardoe@g.o> wrote: |
4 |
> |
5 |
> |
6 |
>> All, |
7 |
>> |
8 |
>> Here's a GLEP for the addition of USE flag descriptions to package |
9 |
>> metadata. It does not address any future ideas that others may have |
10 |
>> had or suggested. It merely gives developers the necessary "tools" to |
11 |
>> document their USE flag usage it better detail on a per package basis. |
12 |
>> |
13 |
>> An clearly motivation explanation that I didn't add, which I'm going |
14 |
>> to add once I send this is the fact that as per the QA Project, |
15 |
>> use.local.desc can not contain a USE flag that already appears |
16 |
>> globally in use.desc. This would allow a description for that USE |
17 |
>> flag to be contained in the metadata. |
18 |
>> |
19 |
>> http://www.gentoo.org/proj/en/glep/glep-0056.html |
20 |
>> |
21 |
>> I encourage any and all _technical_ feedback. |
22 |
>> |
23 |
> |
24 |
> Doesn't include any statement about compability with existing tools or |
25 |
> how it's related to use.local.desc (replacement, extension, ...) |
26 |
> |
27 |
> Marius |
28 |
> |
29 |
It purposefully does not. XML is an extensible language that allows for |
30 |
this type of expandability. Current tools should be able to validate |
31 |
that adding these tags are valid if they appear in the DTD. However, if |
32 |
those tools do not handle those tags they should not do anything with |
33 |
them, hence the nature of XML. |
34 |
|
35 |
The replacement of use.local.desc would necessitate a change to any and |
36 |
all tools which use that file and require them to support the new XML |
37 |
data. This of course introduces a chicken/egg issue. I have mentioned to |
38 |
infra the possibility of having a pre-rsync process that condensed all |
39 |
metadata.xml's into a use.local.desc that would be part of rsync data |
40 |
but not part of CVS. This could be written as a CVS hook to see when a |
41 |
metadata.xml was touched and run the utility appropriately. |
42 |
|
43 |
But again, this is outside the scope of this GLEP, whose purpose merely |
44 |
is to provide a way to document this. |
45 |
-- |
46 |
gentoo-dev@l.g.o mailing list |