1 |
On 03/08/2015 10:01 AM, Joakim Tjernlund wrote: |
2 |
> On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote: |
3 |
>> |
4 |
>> package.use/package.use.force is a bit different though: |
5 |
>> cat /etc/portage/package.use/qemu |
6 |
>> app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr virtfs static- |
7 |
>> user |
8 |
>> |
9 |
>> #Needed by static-user |
10 |
>> sys-libs/zlib static-libs |
11 |
>> dev-libs/glib static-libs |
12 |
>> sys-apps/attr static-libs |
13 |
>> |
14 |
>> Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all |
15 |
>> flags which has a - on them, emerge wants to turn them on again. |
16 |
>> |
17 |
>> Am I missing something? |
18 |
>> Using portage 2.2.18 |
19 |
> |
20 |
> Appears one have to use package.use.mask for that. |
21 |
> cat package.use.mask |
22 |
> app-emulation/qemu alsa pulseaudio bluetooth opengl |
23 |
> It would be handy if one could use the same syntax as in |
24 |
> /etc/portage/package.use/qemu(-alsa -opengl etc.) |
25 |
> |
26 |
> Jocke |
27 |
> |
28 |
|
29 |
Yes, the inverted use.mask logic can be confusing if you are not |
30 |
familiar with it. The negative flags have a special meaning within the |
31 |
context of of portage's "incremental stacking" behavior, so they can |
32 |
still be useful, though not in the same way that you you attempted to |
33 |
use them. |
34 |
-- |
35 |
Thanks, |
36 |
Zac |