IMHO a lot of the auto-use stuff that is "mis-used" is moreso what IUSE
defaults is for. I have a crappy patch for IUSE defaults that I may try
to work on so that it can be merged in the 2.1/2.2 branch. I realize
that this is probably a bit far off, but will hopefully improve the
situation.
Of course at that point we can dump the crappy nocxx flags too ;)
solar wrote:
On Fri, 2006-01-13 at 06:57 -0500, Mike Frysinger wrote:
as one of the new sane features of the next portage-2.1_pre release, we're
looking to cut out use.defaults support
I see this as a good and bad thing. Good in one hand that less autojunk
would be enabled like python/perl bindings not being added to every
program on your system that supports it. Bad in the other hand I see
the state of profiles getting worse=more bloated. The autouse itself is
not a bad feature or idea if it were used properly. Problem is that
it's not been used properly. If it were limited to simple things like
just X and the things that actually make sense then it would even be
fine to keep and would allow some of the more bloated (default-linux)
profiles to be cleaned up. Shrug. I like the existing behavior and the
power of deciding for myself when and where I want to take advantage of
USE_ORDER=
existing stable users wont be affected as the 2.0.x versions will continue to
carry support for this, but some of you stable users may notice some USE
flags suddenly "disappearing"
to recap, use.defaults inserts USE flags for you based upon what packages you
have installed when you havent declared a preference. for example, if you
have neither '-cups' or 'cups' in your USE (either in your make.conf,
profile, env, whatever), but you do have the net-print/cups package
installed, portage will add 'cups' to your USE
-mike
--
[email protected] mailing list
