1 |
Is there some way to set package-specific USE-flags in some config-file |
2 |
somewhere so I don't have to give it manually on the command-line each |
3 |
and every time I want to reemerge or upgrade the package? |
4 |
If not, then that functionality would make my life (and probably many |
5 |
others too) alot easier. I just did an "update world" and after it |
6 |
finished I realised that I had to reemerge a couple of packages since my |
7 |
global USE-flags didn't comply with those I wanted for those specific |
8 |
packages. For example: I don't want QT-support built-in for most of the |
9 |
software on my machine so I have "-qt" in my USE-flag in make.conf, but |
10 |
since I want the qt-gui for licq I have to reemerge licq with USE="qt" |
11 |
after every single time licq is a part of an "update world". And just |
12 |
recently I had to lower the aggressiveness on my CFLAGS to be able to |
13 |
emerge mozilla-firebird. I don't want those slack CFLAGS for most of the |
14 |
packages in my system so I have to give the CFLAGS manually when |
15 |
emerging that package. |
16 |
A suggestion on how to realise it would be package-specific USE-flags in |
17 |
make.conf or some other config-file under /etc. For example: If I |
18 |
would want qt-support in licq then I'd add LICQ_USE="qt" in make.conf or |
19 |
whatever where LICQ_USE is the package-name in uppercase followed by |
20 |
_USE. Since there are support for converting strings to uppercase in |
21 |
python I don't see a problem in implementing this feature. |
22 |
Has there been no request for this feature earlier? Or is there another |
23 |
obstacle in the way of implementing it? |
24 |
|
25 |
Eagerly awaiting your response, |
26 |
Patrick Börjesson |
27 |
|
28 |
P.S. Sorry for the long post. D.S. |
29 |
|
30 |
-- |
31 |
Public key id: 4C5AB0BF |
32 |
Public key available at search.keyserver.net[:11371] |