Gentoo Archives: gentoo-dev

From: Ryan Hill <dirtyepic@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: USE flag documentation
Date: Tue, 15 Jan 2008 23:08:44
Message-Id: fmjed6$t6g$1@ger.gmane.org
In Reply to: Re: [gentoo-dev] Re: USE flag documentation by Vlastimil Babka
1 Vlastimil Babka wrote:
2 > Ryan Hill wrote:
3 >> What do people think of this?
4 >>
5 >> a) Keep use.desc as it is: a list of common flags and a short general
6 >> description of their meaning.
7 >
8 > Good.
9 >
10 >> b) Keep use.local.desc as it is: a list of per-package flags that are
11 >> specific to one to a few ebuilds (i think 5 is the number though i
12 >> think 10 is more appropriate, but that's not relevant to this
13 >> discussion). Again, each has a short description.
14 >>
15 >> c) Allow flags from use.desc to also exist in use.local.desc. In the
16 >> case that a flag for a package exists in both, the use.local.desc
17 >> description overrides the use.desc one. This allows a more specific
18 >> per-package description of global flags.
19 >
20 > Good.
21 >
22 >> d) Allow long descriptions in a package's metadata.xml, as some have
23 >> begun to do already, for cases where more info is needed. For example
24 >> I'd like to explain exactly what the bindist flag on freetype does and
25 >> what legal implications disabling it can have.
26 >
27 > Right. Also why not also add short descriptions there, and deprecate
28 > use.local.desc when tools are converted? Placing package-local info to
29 > global files (when not needed to distinguish profiles as with
30 > package.use.mask etc) is icky.
31 > Note that the metadata.xml should be able to record per-version
32 > differences somehow.
33
34 Then instead of grepping a file I would need to read XML. Also icky. Utils
35 would help, but then utils would need to implement an XML parser.
36
37
38 --
39 fonts, by design, by neglect
40 gcc-porting, for a fact or just for effect
41 wxwindows @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
42
43 --
44 gentoo-dev@l.g.o mailing list