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