| 1 |
On 03/11/2015 08:48 AM, Joakim Tjernlund wrote: |
| 2 |
> On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote: |
| 3 |
>> On 03/08/2015 10:01 AM, Joakim Tjernlund wrote: |
| 4 |
>>> On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote: |
| 5 |
>>>> |
| 6 |
>>>> package.use/package.use.force is a bit different though: |
| 7 |
>>>> cat /etc/portage/package.use/qemu |
| 8 |
>>>> app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr virtfs |
| 9 |
>>>> static- |
| 10 |
>>>> user |
| 11 |
>>>> |
| 12 |
>>>> #Needed by static-user |
| 13 |
>>>> sys-libs/zlib static-libs |
| 14 |
>>>> dev-libs/glib static-libs |
| 15 |
>>>> sys-apps/attr static-libs |
| 16 |
>>>> |
| 17 |
>>>> Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all |
| 18 |
>>>> flags which has a - on them, emerge wants to turn them on again. |
| 19 |
>>>> |
| 20 |
>>>> Am I missing something? |
| 21 |
>>>> Using portage 2.2.18 |
| 22 |
>>> |
| 23 |
>>> Appears one have to use package.use.mask for that. |
| 24 |
>>> cat package.use.mask |
| 25 |
>>> app-emulation/qemu alsa pulseaudio bluetooth opengl |
| 26 |
>>> It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-alsa -opengl etc.) |
| 27 |
>>> |
| 28 |
>>> Jocke |
| 29 |
>>> |
| 30 |
>> |
| 31 |
>> Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The negative flags have a |
| 32 |
>> special meaning within the context of of portage's "incremental stacking" behavior, so they can still be |
| 33 |
>> useful, though not in the same way that you you attempted to use them. |
| 34 |
> |
| 35 |
> |
| 36 |
> So now I got to binary pkgs and profiles, the profile is typically part of ebuild src tree/overlay |
| 37 |
> and a system using only binary pkgs does not need ebuild sources. How does one manage profiles |
| 38 |
> is this case? |
| 39 |
> Just sync an empty /usr/portage tree(sans profile) or is the a better way? |
| 40 |
|
| 41 |
Recent portage has emerge --sync --sync-submodule=profile, which might |
| 42 |
be useful. I would like to work toward handling this case better, so |
| 43 |
your feedback is welcome. |
| 44 |
|
| 45 |
> |
| 46 |
> Jocke |
| 47 |
> |
| 48 |
> PS. |
| 49 |
> emerge --depclean refuses to clean a system which is lagging behind, would it be possible for |
| 50 |
> --depclean to go ahead anyway somehow? --dynamic-deps=n comes to mind. |
| 51 |
|
| 52 |
You should probably put --dynamic-deps=n in EMERGE_DEFAULT_OPTS, since |
| 53 |
this option typically causes these kinds of problems with --depclean. |
| 54 |
You don't need --dynamic-deps if you use --changed-deps when updating. |
| 55 |
-- |
| 56 |
Thanks, |
| 57 |
Zac |
Archives