| 1 |
> |
| 2 |
>Actually, I'd find it useful personally. |
| 3 |
>People add *weird* use flags sometimes. |
| 4 |
> |
| 5 |
> |
| 6 |
LoL... yes, thats true. |
| 7 |
|
| 8 |
A suggestion possibly to keep in mind is what if all functionality |
| 9 |
related to USE flags were somehow implemented in a seperate class/set of |
| 10 |
functions... or maybe that's already being done. But I mean, the job of |
| 11 |
determining which flags apply to what package and managing all that and |
| 12 |
how it works... I noticed that (at least in stable) a lot of it is in |
| 13 |
portage.config, but maybe it could be a seperate class that |
| 14 |
portage.config uses.. and other things (like deps, etc). Then stuff like |
| 15 |
outputting USE flags, or adding additional ways to determine which USE |
| 16 |
flags to actually use for each package, would all be in one location, |
| 17 |
lending itself to code reuse... |
| 18 |
|
| 19 |
Of course, this is just from my looking at portage stable for a week or |
| 20 |
so... maybe its already being done. :) |
| 21 |
|
| 22 |
Dustin |
| 23 |
-- |
| 24 |
gentoo-portage-dev@g.o mailing list |
Archives