Ciaran McCreesh wrote:
On Sun, 15 Oct 2006 18:59:27 -0400 Alec Warner <[EMAIL PROTECTED]>
wrote:
| I don't see how the location of the default USE affects these things.
Searching across an entire tree, plus in things that can be defined in
eclasses, is a pain in the ass.
| However I still believe there exist examples where default USE in an
| ebuild is a better solution.
Such as?
A circumstance where not having the flag on causes unexpected behavior.
Say compiling gcc without C++ support. The majority of use cases out
there, C++ support is a requirement. Thus you enable it in the ebuild;
because the chance of someone moving it into another overlay/repo and
then getting a screwed system is rather high.
The ebuild itself should be "sane" with no profile surrounding it.
--
[email protected] mailing list
