Actually, I'd find it useful personally.
People add *weird* use flags sometimes.
LoL... yes, thats true.
A suggestion possibly to keep in mind is what if all functionality
related to USE flags were somehow implemented in a seperate class/set of
functions... or maybe that's already being done. But I mean, the job of
determining which flags apply to what package and managing all that and
how it works... I noticed that (at least in stable) a lot of it is in
portage.config, but maybe it could be a seperate class that
portage.config uses.. and other things (like deps, etc). Then stuff like
outputting USE flags, or adding additional ways to determine which USE
flags to actually use for each package, would all be in one location,
lending itself to code reuse...
Of course, this is just from my looking at portage stable for a week or
so... maybe its already being done. :)
Dustin
--
[email protected] mailing list
