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