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