| 1 |
On 13:11 Wed 13 Aug , Doug Goldstein wrote: |
| 2 |
> Further questions regarding use.desc have come up with regard to this |
| 3 |
> GLEP. My proposed solution would be a potential amendment to the GLEP to |
| 4 |
> state that |
| 5 |
> |
| 6 |
> <flag name='png' /> |
| 7 |
> |
| 8 |
> Would be allowed. This syntax is not actually disallowed or allowed by |
| 9 |
> the current GLEP, but mentioning it would allow a metadata.xml contain |
| 10 |
> all the USE flags that appear in IUSE, even the global ones. By using |
| 11 |
> the above syntax, it would simply state that there is no additional |
| 12 |
> descriptions or details but to just use the use.desc description. |
| 13 |
> |
| 14 |
> Further more, it would allow us in the future to make that mandatory and |
| 15 |
> repoman would only have to check metadata.xml for your USE flag. |
| 16 |
|
| 17 |
It seems like this doesn't have much benefit and is a bit confusing to |
| 18 |
me. You now need to know which flags in metadata.xml are global so you |
| 19 |
don't allow descriptions for them. You also need to verify the globals |
| 20 |
between the two places they'll be specified (metadata.xml and use.desc |
| 21 |
for the description) so you don't have things claiming they're global |
| 22 |
but aren't. The benefit here doesn't end up saving anything at all once |
| 23 |
you have a consistency check anyway. |
| 24 |
|
| 25 |
Halcy0n also mentioned that this gets really annoying when USE flags |
| 26 |
inherited from eclasses change. You'd need to edit every metadata.xml of |
| 27 |
all inheriting packages. |
| 28 |
|
| 29 |
-- |
| 30 |
Thanks, |
| 31 |
Donnie |
| 32 |
|
| 33 |
Donnie Berkholz |
| 34 |
Developer, Gentoo Linux |
| 35 |
Blog: http://dberkholz.wordpress.com |
Archives