| 1 |
Ryan Hill <dirtyepic@g.o> said: |
| 2 |
> a) Keep use.desc as it is: a list of common flags and a short general |
| 3 |
> description of their meaning. |
| 4 |
|
| 5 |
Sounds good. |
| 6 |
|
| 7 |
> b) Keep use.local.desc as it is: a list of per-package flags that are |
| 8 |
> specific to one to a few ebuilds (i think 5 is the number though i think 10 |
| 9 |
> is more appropriate, but that's not relevant to this discussion). Again, |
| 10 |
> each has a short description. |
| 11 |
|
| 12 |
Also fine. |
| 13 |
|
| 14 |
> c) Allow flags from use.desc to also exist in use.local.desc. In the case |
| 15 |
> that a flag for a package exists in both, the use.local.desc description |
| 16 |
> overrides the use.desc one. This allows a more specific per-package |
| 17 |
> description of global flags. |
| 18 |
|
| 19 |
Still doing alright :) |
| 20 |
|
| 21 |
> d) Allow long descriptions in a package's metadata.xml, as some have begun |
| 22 |
> to do already, for cases where more info is needed. For example I'd like |
| 23 |
> to explain exactly what the bindist flag on freetype does and what legal |
| 24 |
> implications disabling it can have. |
| 25 |
|
| 26 |
Why can't this be done in use.local.desc? |
| 27 |
|
| 28 |
-- |
| 29 |
Mark Loeser |
| 30 |
email - halcy0n AT gentoo DOT org |
| 31 |
email - mark AT halcy0n DOT com |
| 32 |
web - http://www.halcy0n.com |
Archives