Grant Edwards wrote:
I probably shouldn't admit this in public, but I've been fighting with
Portage over qt3 support for a long time (at least a year). I was
constantly being told by Portage to either enable or disable the
qt3support use flag for some package or other. I usually just gave up
and uninstalled all of the apps that needed qt3 support (until I
needed that app the next time -- then the fight started all over
again).
After stumbling around this issue on several machines for way too
long, I finally stumbled across the solution: don't enable/disable
qt3support on a per-package basis. If you want qt3support put it in
/etc/make.conf. Despite the fact that portage will tell you to enable
qt3support for package XYZ, doing just that won't work.
Perhaps this sounds obvious, but it sure took me a long time to figure
it out...
I rarely put a USE flag in anything but make.conf. Usually, if I need
support for something, it is more than one package or that one package
will want the support enabled for other packages it builds on as well.
I have disabled a USE flag in package.use before tho. That seems to
work OK almost all the time. -doc and -hal come to mind without even
looking at the file.
Glad you got it figured out tho. At least by learning it the hard way,
you won't forget it. ;-)
Dale
:-) :-)
