| 1 |
Mike Frysinger wrote: |
| 2 |
|
| 3 |
> Paul Varner wrote: |
| 4 |
>> Robin H. Johnson wrote: |
| 5 |
>> > Why are we keeping it? I move that we remove it. It's been replaced |
| 6 |
>> > by USE flags in metadata.xml for several years now. |
| 7 |
>> |
| 8 |
>> euse from gentoolkit still uses it since it is written in bash and XML |
| 9 |
>> parsing in bash can be problematic. We really need to get euse |
| 10 |
>> rewritten in python so it can use the portage and gentoolkit API's |
| 11 |
>> before we get rid of the file. |
| 12 |
> |
| 13 |
> it's also a bit of a speed issue. i often want to look at what flags get |
| 14 |
> used |
| 15 |
> across the tree. what's faster: loading + parsing 15000 xml files, or |
| 16 |
> loading 1 file ? shifting it to metadata/ as a cache of all the xml files |
| 17 |
> is probably fine, but i'm not sure dropping it completely is an |
| 18 |
> improvement. -mike |
| 19 |
|
| 20 |
Agreed. I don't think it's a good idea to lose the ability to script against |
| 21 |
the tree from bash. |
| 22 |
|
| 23 |
Portage itself has always made it easy for the user to write custom sys- |
| 24 |
admin scripts, and use.local.desc aids in that. |
| 25 |
|
| 26 |
-- |
| 27 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |
Archives