1 |
On 03/14/2015 11:41 AM, Joakim Tjernlund wrote: |
2 |
> On Sat, 2015-03-14 at 11:08 -0700, Zac Medico wrote: |
3 |
>> On 03/14/2015 09:12 AM, Joakim Tjernlund wrote: |
4 |
>>> On Wed, 2015-03-11 at 13:43 -0700, Zac Medico wrote: |
5 |
>>>> On 03/11/2015 01:16 PM, Joakim Tjernlund wrote: |
6 |
>>>>> On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote: |
7 |
>>>>>> On 03/11/2015 08:48 AM, Joakim Tjernlund wrote: |
8 |
>>>>>>> On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote: |
9 |
>>>>>>>> On 03/08/2015 10:01 AM, Joakim Tjernlund wrote: |
10 |
>>>>>>>>> On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote: |
11 |
>>>>>>>>>> |
12 |
>>>>>>>>>> package.use/package.use.force is a bit different though: |
13 |
>>>>>>>>>> cat /etc/portage/package.use/qemu |
14 |
>>>>>>>>>> app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr |
15 |
>>>>>>>>>> virtfs |
16 |
>>>>>>>>>> static- |
17 |
>>>>>>>>>> user |
18 |
>>>>>>>>>> |
19 |
>>>>>>>>>> #Needed by static-user |
20 |
>>>>>>>>>> sys-libs/zlib static-libs |
21 |
>>>>>>>>>> dev-libs/glib static-libs |
22 |
>>>>>>>>>> sys-apps/attr static-libs |
23 |
>>>>>>>>>> |
24 |
>>>>>>>>>> Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl |
25 |
>>>>>>>>>> all |
26 |
>>>>>>>>>> flags which has a - on them, emerge wants to turn them on again. |
27 |
>>>>>>>>>> |
28 |
>>>>>>>>>> Am I missing something? |
29 |
>>>>>>>>>> Using portage 2.2.18 |
30 |
>>>>>>>>> |
31 |
>>>>>>>>> Appears one have to use package.use.mask for that. |
32 |
>>>>>>>>> cat package.use.mask |
33 |
>>>>>>>>> app-emulation/qemu alsa pulseaudio bluetooth opengl |
34 |
>>>>>>>>> It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-alsa - |
35 |
>>>>>>>>> opengl |
36 |
>>>>>>>>> etc.) |
37 |
>>>>>>>>> |
38 |
>>>>>>>>> Jocke |
39 |
>>>>>>>>> |
40 |
>>>>>>>> |
41 |
>>>>>>>> Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The negative |
42 |
>>>>>>>> flags |
43 |
>>>>>>>> have a |
44 |
>>>>>>>> special meaning within the context of of portage's "incremental stacking" behavior, so they can |
45 |
>>>>>>>> still |
46 |
>>>>>>>> be |
47 |
>>>>>>>> useful, though not in the same way that you you attempted to use them. |
48 |
>>> |
49 |
>>> Just noticed that USE flags in profiles/package.use.mask override everything so this |
50 |
>>> USE=thin emerge -av sys-fs/lvm2 |
51 |
>>> will not turn on thin if thin is in profiles/package.use.mask |
52 |
>>> How can just change the default so a user can easily turn it on ? |
53 |
>> |
54 |
>> Generally, setting the USE environment variable like that is poor practice, because the setting will not |
55 |
>> persist the next time that you rebuild the package. So, you should set the flag in |
56 |
> |
57 |
> |
58 |
> I know, this was just an example to illustrate that it did not work. |
59 |
> |
60 |
>> /etc/portage/package.use. You can unmask the flag for lvm2 like this: |
61 |
>> |
62 |
>> echo "sys-fs/lvm2 -thin" >> /etc/portage/profile/package.use.mask |
63 |
> |
64 |
> You misunderstand, I have "sys-fs/lvm2 thin" in /etc/portage/profile/package.use.mask |
65 |
> and I want a user to able to override this setting, using USE=".." or adding it |
66 |
> to their local /etc/portage/package.use file/dir |
67 |
|
68 |
There's no other way to negate a use mask than to use |
69 |
/etc/portage/profile/{use.mask,package.use.mask} as I have described. I |
70 |
don't think that it makes much sense to negate a use mask for a single |
71 |
emerge invocation. If you want to do that, then why is the use flag |
72 |
masked anyway? |
73 |
-- |
74 |
Thanks, |
75 |
Zac |