Am Dienstag, 29. Juli 2014, 19:04:04 schrieb behrouz khosravi: > > Now I am thinking about managing USE flags. > What if I disable everything in the make.conf ( I mean USE="-*" ) and > gradually add the needed flags to package.use?
The default profile is what you need. Please don't do USE="-*". It breaks things. * Long ago, setting a useflag always meant "adding things to the default". For some years now, we have use-defaults, which means an ebuild can set whether a use flag set not by profile and not by user is on or off. If you add "-*" to your use flags, you turn all default-on useflags off too (which means you may switch away from upstream defaults a lot). An example where this may lead to trouble: you end up with sys-devel/gcc[- cxx], i.e. a compiler that cannot translate C++. * The dependencies on specific Python or Ruby versions are controlled via useflags. Basically, if Python package X needs Python package Y, both have to be installed for the same Python variant for things to work. If you disable all useflags via "-*", you basically disable support for all variants. Bang. * Similar for multilib installations. -- Andreas K. Huettel Gentoo Linux developer dilfri...@gentoo.org http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
