Nikos Chantziaras wrote:
On 10/02/2011 12:14 PM, Dale wrote:
Nikos Chantziaras wrote:
On 10/02/2011 11:44 AM, Dale wrote:
Look into app-portage/ufed.
Hey, cooool. That is some cool stuff. Maybe I can use this to clean
this
up:
USE="3dnow 3dnowext X a52 aac acpi alsa amd64 aml apng automount avahi
[snip monstrosity]
It seems you confused make.conf with package.use :-P
I rarely use package.use. There is a couple lines in there but not many.
I usually enable a USE flag globally in make.conf and be done with it.
Which results in the above chaos ;-P The obvious problem is that
sometimes you enable a USE flag for some package, but that USE flag
has an effect on other packages too if you put it in make.conf, even
though you might not want that. One reason you might not want that
are bloated dependencies. For example, you install package "foo" and
you want the "bar" USE flag for it. If you put it in make.conf, other
packages might also use that flag and pull-in its deps. Now if you
unmerge "foo", an emerge --depclean will not uninstall those deps. As
time goes on, this results in a system full of deps you never really
wanted and can't get rid of.
In that case, I then use package.use. Like this in package.use:
x11-base/xorg-server -hal
net-misc/ntp caps -ipv6
media-gfx/gtkam debug
sys-power/nut -usb
I use package.use for those exceptions where I don't want something.
Otherwise, I put it in make.conf so that I only have one file to deal
with for the most part.
I am OCD about some things, like brakes on my car, but I'm not that OCD
about this one. I do wish emerge would give notice when a USE flag is
invalid tho. It's nice that it just ignores it and goes on but a little
message that one has fell off the list would be nice.
To each his own I guess. This is how I been managing my USE flags since
about 2003 and it works rather well. At least for me. ;-)
Dale
:-) :-)
