On Feb 6, 2004, at 7:14 pm, Paul de Vrieze wrote:
One other thing to this respect. What do you (multiple) think about allowing
the description of the useflags in the metadata.xml file? (or in the ebuild
itself) That would allow specification of what the consequenses are for
choosing that flag for this ebuild.
Mmmmm... I *like* that. It's be really nice to `emerge -pvv someapp` and see exactly what each USE flag does, relevant to the ebuild that's depending on it. Y'know like "+gtk " builds GUI as well as default console app" would be perfect.
There's a little bit of me that's saying "But that might encourage diversion in the use of USE flags for different ebuilds", but I suspect that may be happening already.
I don't recall enough of the discussion of the -vim-with-x USE flag... I seem to have an idea that (with the same USE flag) some ebuilds will pull in extra dependencies and others will only change the `make` options without pulling any other packages. Is this the case..? I don't really think that necessarily needs separate kinds of USE flags, but it would help if one could see the difference at a glance.
Stroller.
-- [EMAIL PROTECTED] mailing list
