Peter Gordon wrote:
Zac Medico wrote:
The difference with use.force is that it prevents flags, that are deemed
extremely important, from being accidentally disabled by the user.
If they were so "extremely important" then they would not be optional,
and hence not even be USE flags at all, no? Or am I missing something?
Hmm... I set out to build a system recently (since 2006.0) with
USE="-*", just to see if I could. After borking python a couple of
times (you know how it is ;)), I was prevented from completing system by
a couple of ebuilds failing on not having c++ available. One was bison,
which failed on one of its examples rather than on the program itself.
I can't remember what the other package was, but it was a C-only package
(yacc maybe? or did it begin with a 'g'?) that failed in configure - I
remember wondering where the "Removing useless C++ checks" message was
when I needed it. Around about then I stopped having spare time, so I
never filed bugs or investigated further.
My point, now that I've bored you all with a long story, is that if
you're careful about it, no USE flag is *truly* required, at least for a
working system. Sure, some are highly recommended - but isn't that what
defaults are for? :)
--
gentoo-dev@gentoo.org mailing list
