[gentoo-portage-dev] custom profiles?

[gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

I am trying to define a custom profile in one of our overlay(managed via layman)
This profile should inherit one of /usr/portage/profiles/ and
then I want to add custom USE flags, mask, keywords packages etc, then eselect this new profile.

I cannot work out how to do this, any pointers?
portage: 2.2.18

 Jocke

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/06/2015 02:15 AM, Joakim Tjernlund wrote:
> I am trying to define a custom profile in one of our overlay(managed via layman)
> This profile should inherit one of /usr/portage/profiles/ and
> then I want to add custom USE flags, mask, keywords packages etc, then eselect this new profile.
> 
> I cannot work out how to do this, any pointers?
> portage: 2.2.18
> 
>  Jocke
> 

Set "profile-formats = portage-2" in metadata/layout.conf of your
overlay. The is documented in the "portage" man page. It allows you to
specify a profile from another repository in the "parent" file of you
profile. For example, gentoo:default/linux/amd64/13.0/desktop in your
"parent" file will cause your overlay's profile to inherit from that
gentoo profile. If you list your profiles in profiles/profiles.desc in
you overlay, then eselect profile will see them.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Sat, 2015-03-07 at 12:18 -0800, Zac Medico wrote:
> On 03/06/2015 02:15 AM, Joakim Tjernlund wrote:
> > I am trying to define a custom profile in one of our overlay(managed via layman)
> > This profile should inherit one of /usr/portage/profiles/ and
> > then I want to add custom USE flags, mask, keywords packages etc, then eselect this new profile.
> > 
> > I cannot work out how to do this, any pointers?
> > portage: 2.2.18
> > 
> >  Jocke
> > 
> 
> Set "profile-formats = portage-2" in metadata/layout.conf of your overlay. The is documented in the 
> "portage" man page. It allows you to specify a profile from another repository in the "parent" file of you 
> profile. For example, gentoo:default/linux/amd64/13.0/desktop in your "parent" file will cause your 
> overlay's profile to inherit from that gentoo profile. If you list your profiles in profiles/profiles.desc 
> in you overlay, then eselect profile will see them.

Thanks Zac, I did the above and got my own profile :)

I can get package.accept_keywords work the same as my keyword installed at
/etc/portage/package.keywords.

package.use/package.use.force is a bit different though:
cat /etc/portage/package.use/qemu
app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr virtfs static-user

#Needed by static-user
sys-libs/zlib static-libs
dev-libs/glib static-libs
sys-apps/attr static-libs

Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all
flags which has a - on them, emerge wants to turn them on again.

Am I missing something?
Using portage 2.2.18

 Jocke

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
> On Sat, 2015-03-07 at 12:18 -0800, Zac Medico wrote:
> > On 03/06/2015 02:15 AM, Joakim Tjernlund wrote:
> > > I am trying to define a custom profile in one of our overlay(managed via layman)
> > > This profile should inherit one of /usr/portage/profiles/ and
> > > then I want to add custom USE flags, mask, keywords packages etc, then eselect this new profile.
> > > 
> > > I cannot work out how to do this, any pointers?
> > > portage: 2.2.18
> > > 
> > >  Jocke
> > > 
> > 
> > Set "profile-formats = portage-2" in metadata/layout.conf of your overlay. The is documented in the 
> > "portage" man page. It allows you to specify a profile from another repository in the "parent" file of 
> > you 
> > profile. For example, gentoo:default/linux/amd64/13.0/desktop in your "parent" file will cause your 
> > overlay's profile to inherit from that gentoo profile. If you list your profiles in 
> > profiles/profiles.desc 
> > in you overlay, then eselect profile will see them.
> 
> Thanks Zac, I did the above and got my own profile :)
> 
> I can get package.accept_keywords work the same as my keyword installed at
> /etc/portage/package.keywords.
> 
> package.use/package.use.force is a bit different though:
> cat /etc/portage/package.use/qemu
> app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr virtfs static-
> user
> 
> #Needed by static-user
> sys-libs/zlib static-libs
> dev-libs/glib static-libs
> sys-apps/attr static-libs
> 
> Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all
> flags which has a - on them, emerge wants to turn them on again.
> 
> Am I missing something?
> Using portage 2.2.18

Appears one have to use package.use.mask for that.
 cat package.use.mask
 app-emulation/qemu alsa pulseaudio bluetooth opengl
It would be handy if one could use the same syntax as in
/etc/portage/package.use/qemu(-alsa -opengl etc.)

 Jocke

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
> On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
>>
>> package.use/package.use.force is a bit different though:
>> cat /etc/portage/package.use/qemu
>> app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr virtfs static-
>> user
>>
>> #Needed by static-user
>> sys-libs/zlib static-libs
>> dev-libs/glib static-libs
>> sys-apps/attr static-libs
>>
>> Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all
>> flags which has a - on them, emerge wants to turn them on again.
>>
>> Am I missing something?
>> Using portage 2.2.18
> 
> Appears one have to use package.use.mask for that.
>  cat package.use.mask
>  app-emulation/qemu alsa pulseaudio bluetooth opengl
> It would be handy if one could use the same syntax as in
> /etc/portage/package.use/qemu(-alsa -opengl etc.)
> 
>  Jocke
> 

Yes, the inverted use.mask logic can be confusing if you are not
familiar with it. The negative flags have a special meaning within the
context of of portage's "incremental stacking" behavior, so they can
still be useful, though not in the same way that you you attempted to
use them.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
> On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
> > On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
> > > 
> > > package.use/package.use.force is a bit different though:
> > > cat /etc/portage/package.use/qemu
> > > app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr virtfs 
> > > static-
> > > user
> > > 
> > > #Needed by static-user
> > > sys-libs/zlib static-libs
> > > dev-libs/glib static-libs
> > > sys-apps/attr static-libs
> > > 
> > > Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all
> > > flags which has a - on them, emerge wants to turn them on again.
> > > 
> > > Am I missing something?
> > > Using portage 2.2.18
> > 
> > Appears one have to use package.use.mask for that.
> >  cat package.use.mask
> >  app-emulation/qemu alsa pulseaudio bluetooth opengl
> > It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-alsa -opengl etc.)
> > 
> >  Jocke
> > 
> 
> Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The negative flags have a
> special meaning within the context of of portage's "incremental stacking" behavior, so they can still be 
> useful, though not in the same way that you you attempted to use them.


So now I got to binary pkgs and profiles, the profile is typically part of ebuild src tree/overlay
and a system using only binary pkgs does not need ebuild sources. How does one manage profiles
is this case?
Just sync an empty /usr/portage tree(sans profile) or is the a better way?


 Jocke

PS.
    emerge --depclean refuses to clean a system which is lagging behind, would it be possible for
    --depclean to go ahead anyway somehow? --dynamic-deps=n comes to mind.

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
> On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
>> On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
>>> On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
>>>>
>>>> package.use/package.use.force is a bit different though:
>>>> cat /etc/portage/package.use/qemu
>>>> app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr virtfs 
>>>> static-
>>>> user
>>>>
>>>> #Needed by static-user
>>>> sys-libs/zlib static-libs
>>>> dev-libs/glib static-libs
>>>> sys-apps/attr static-libs
>>>>
>>>> Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all
>>>> flags which has a - on them, emerge wants to turn them on again.
>>>>
>>>> Am I missing something?
>>>> Using portage 2.2.18
>>>
>>> Appears one have to use package.use.mask for that.
>>>  cat package.use.mask
>>>  app-emulation/qemu alsa pulseaudio bluetooth opengl
>>> It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-alsa -opengl etc.)
>>>
>>>  Jocke
>>>
>>
>> Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The negative flags have a
>> special meaning within the context of of portage's "incremental stacking" behavior, so they can still be 
>> useful, though not in the same way that you you attempted to use them.
> 
> 
> So now I got to binary pkgs and profiles, the profile is typically part of ebuild src tree/overlay
> and a system using only binary pkgs does not need ebuild sources. How does one manage profiles
> is this case?
> Just sync an empty /usr/portage tree(sans profile) or is the a better way?

Recent portage has emerge --sync --sync-submodule=profile, which might
be useful. I would like to work toward handling this case better, so
your feedback is welcome.

> 
>  Jocke
> 
> PS.
>     emerge --depclean refuses to clean a system which is lagging behind, would it be possible for
>     --depclean to go ahead anyway somehow? --dynamic-deps=n comes to mind.

You should probably put --dynamic-deps=n in EMERGE_DEFAULT_OPTS, since
this option typically causes these kinds of problems with --depclean.
You don't need --dynamic-deps if you use --changed-deps when updating.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
> On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
> > On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
> > > On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
> > > > On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
> > > > > 
> > > > > package.use/package.use.force is a bit different though:
> > > > > cat /etc/portage/package.use/qemu
> > > > > app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr virtfs 
> > > > > static-
> > > > > user
> > > > > 
> > > > > #Needed by static-user
> > > > > sys-libs/zlib static-libs
> > > > > dev-libs/glib static-libs
> > > > > sys-apps/attr static-libs
> > > > > 
> > > > > Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all
> > > > > flags which has a - on them, emerge wants to turn them on again.
> > > > > 
> > > > > Am I missing something?
> > > > > Using portage 2.2.18
> > > > 
> > > > Appears one have to use package.use.mask for that.
> > > >  cat package.use.mask
> > > >  app-emulation/qemu alsa pulseaudio bluetooth opengl
> > > > It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-alsa -opengl 
> > > > etc.)
> > > > 
> > > >  Jocke
> > > > 
> > > 
> > > Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The negative flags 
> > > have a
> > > special meaning within the context of of portage's "incremental stacking" behavior, so they can still 
> > > be 
> > > useful, though not in the same way that you you attempted to use them.
> > 
> > 
> > So now I got to binary pkgs and profiles, the profile is typically part of ebuild src tree/overlay
> > and a system using only binary pkgs does not need ebuild sources. How does one manage profiles
> > is this case?
> > Just sync an empty /usr/portage tree(sans profile) or is the a better way?
> 
> Recent portage has emerge --sync --sync-submodule=profile, which might be useful. I would like to work 
> toward handling this case better, so your feedback is welcome.

That would the same as pointing portage to your own empty tree(sans profile). I was hoping for
something connected to your BINHOST so one can get all in one go and stored in the same directory
tree.

> 
> > 
> >  Jocke
> > 
> > PS.
> >     emerge --depclean refuses to clean a system which is lagging behind, would it be possible for
> >     --depclean to go ahead anyway somehow? --dynamic-deps=n comes to mind.
> 
> You should probably put --dynamic-deps=n in EMERGE_DEFAULT_OPTS, since this option 
> typically causes these kinds of problems with --depclean. You don't need --dynamic-deps if you use --
> changed-deps when updating.

If I do --dynamic-deps=n then man emerge suggest to also do fixpackages(I guess after every SYNC)
which feels a bit heavy, is this still needed?

Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing
something here, an example would be great:)  

Will --depclean with --dynamic-deps=n always succeed? I realize that it could be dangerous but
sometimes would like to have the option.


BTW, this text is hard to parse:
--binpkg-changed-deps [ y | n ]
              Tells  emerge  to ignore binary packages for which the corresponding ebuild depen‐
              dencies have changed since the packages were built.  In order to help avoid issues
              with  resolving  inconsistent  dependencies,  this option is automatically enabled
              unless the --usepkgonly option  is  enabled.  Behavior  with  respect  to  changed
              build-time dependencies is controlled by the --with-bdeps option.

--binpkg-changed-deps=y -> Ignore bin pkgs with changed deps?

Re: [gentoo-portage-dev] custom profiles?

[Brian Dolbec]

On Wed, 11 Mar 2015 20:16:06 +0000
Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:

> On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
> > On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
> > > On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
> > > > On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
> > > > > On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
> > > > > > 
> > > > > > package.use/package.use.force is a bit different though:
> > > > > > cat /etc/portage/package.use/qemu
> > > > > > app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl
> > > > > > qemu_user_targets_x86_64 xattr virtfs static-
> > > > > > user
> > > > > > 
> > > > > > #Needed by static-user
> > > > > > sys-libs/zlib static-libs
> > > > > > dev-libs/glib static-libs
> > > > > > sys-apps/attr static-libs
> > > > > > 
> > > > > > Moving this to package.use/package.use.force does not
> > > > > > respect -alsa, -pulseaudio, -opengl all flags which has a -
> > > > > > on them, emerge wants to turn them on again.
> > > > > > 
> > > > > > Am I missing something?
> > > > > > Using portage 2.2.18
> > > > > 
> > > > > Appears one have to use package.use.mask for that.
> > > > >  cat package.use.mask
> > > > >  app-emulation/qemu alsa pulseaudio bluetooth opengl
> > > > > It would be handy if one could use the same syntax as
> > > > > in /etc/portage/package.use/qemu(-alsa -opengl etc.)
> > > > > 
> > > > >  Jocke
> > > > > 
> > > > 
> > > > Yes, the inverted use.mask logic can be confusing if you are
> > > > not familiar with it. The negative flags have a
> > > > special meaning within the context of of portage's "incremental
> > > > stacking" behavior, so they can still be 
> > > > useful, though not in the same way that you you attempted to
> > > > use them.
> > > 
> > > 
> > > So now I got to binary pkgs and profiles, the profile is
> > > typically part of ebuild src tree/overlay and a system using only
> > > binary pkgs does not need ebuild sources. How does one manage
> > > profiles is this case? Just sync an empty /usr/portage tree(sans
> > > profile) or is the a better way?
> > 
> > Recent portage has emerge --sync --sync-submodule=profile, which
> > might be useful. I would like to work toward handling this case
> > better, so your feedback is welcome.
> 
> That would the same as pointing portage to your own empty tree(sans
> profile). I was hoping for something connected to your BINHOST so one
> can get all in one go and stored in the same directory tree.
> 
> > 
> > > 
> > >  Jocke
> > > 
> > > PS.
> > >     emerge --depclean refuses to clean a system which is lagging
> > > behind, would it be possible for --depclean to go ahead anyway
> > > somehow? --dynamic-deps=n comes to mind.
> > 
> > You should probably put --dynamic-deps=n in EMERGE_DEFAULT_OPTS,
> > since this option typically causes these kinds of problems with
> > --depclean. You don't need --dynamic-deps if you use --
> > changed-deps when updating.
> 
> If I do --dynamic-deps=n then man emerge suggest to also do
> fixpackages(I guess after every SYNC) which feels a bit heavy, is
> this still needed?
> 
> Why is --dynamic-deps=y default? This feels like lying about your
> true deps, I am probably missing something here, an example would be
> great:)  


Because the last time we even discussed the possibility of changing
this and steps that might be to fix problems,...  There were a few
individuals that raised such a stink about it, they even brought it to
council to have us STOPPED.

So, as a result much of the portage team don't feel like working on
portage.  Heaven forbid we actually make a change!


> 
> Will --depclean with --dynamic-deps=n always succeed? I realize that
> it could be dangerous but sometimes would like to have the option.
> 
> 
> BTW, this text is hard to parse:
> --binpkg-changed-deps [ y | n ]
>               Tells  emerge  to ignore binary packages for which the
> corresponding ebuild depen‐ dencies have changed since the packages
> were built.  In order to help avoid issues with  resolving
> inconsistent  dependencies,  this option is automatically enabled
> unless the --usepkgonly option  is  enabled.  Behavior  with
> respect  to  changed build-time dependencies is controlled by the
> --with-bdeps option.
> 
> --binpkg-changed-deps=y -> Ignore bin pkgs with changed deps?


-- 
Brian Dolbec <dolsen>

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/11/2015 01:27 PM, Brian Dolbec wrote:
> On Wed, 11 Mar 2015 20:16:06 +0000
> Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:
>> Why is --dynamic-deps=y default? This feels like lying about your
>> true deps, I am probably missing something here, an example would be
>> great:)  
> 
> 
> Because the last time we even discussed the possibility of changing
> this and steps that might be to fix problems,...  There were a few
> individuals that raised such a stink about it, they even brought it to
> council to have us STOPPED.

Well, stuff like this happens when you have lots of users. On the bright
side, at least we have users! Something similar happened when I tried to
make emerge --quiet-build the default.

> So, as a result much of the portage team don't feel like working on
> portage.  Heaven forbid we actually make a change!

It's not so bad, considering that you can simply use --dynamic-deps=n if
you want, and now --changed-deps makes it feasible regardless of what
ebuild developers do.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Wed, 2015-03-11 at 13:48 -0700, Zac Medico wrote:
> On 03/11/2015 01:27 PM, Brian Dolbec wrote:
> > On Wed, 11 Mar 2015 20:16:06 +0000
> > Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:
> > > Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing 
> > > something here, an example would be great:)  
> > 
> > 
> > Because the last time we even discussed the possibility of changing this and steps that might be to fix 
> > problems,...  There were a few individuals that raised such a stink about it, they even brought it to 
> > council to have us STOPPED.
> 
> Well, stuff like this happens when you have lots of users. On the bright side, at least we have users! 
> Something similar happened when I tried to make emerge --quiet-build the default.
> 
> > So, as a result much of the portage team don't feel like working on portage.  Heaven forbid we actually 
> > make a change!
> 
> It's not so bad, considering that you can simply use --dynamic-deps=n if you want, and now --changed-deps 
> makes it feasible regardless of what ebuild developers do.

Oops, seems like I stumbled into a delicate area.
Anyhow, thanks for clarifying this. I will change Transmode defaults to --dynamic-deps=n and
see what happens.
Maybe a gentle push for --dynamic-deps=n in the man page could be the way forward?

 Jocke

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Wed, 2015-03-11 at 21:02 +0000, Joakim Tjernlund wrote:
> On Wed, 2015-03-11 at 13:48 -0700, Zac Medico wrote:
> > On 03/11/2015 01:27 PM, Brian Dolbec wrote:
> > > On Wed, 11 Mar 2015 20:16:06 +0000
> > > Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:
> > > > Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing 
> > > > something here, an example would be great:)  
> > > 
> > > 
> > > Because the last time we even discussed the possibility of changing this and steps that might be to fix 
> > > problems,...  There were a few individuals that raised such a stink about it, they even brought it to 
> > > council to have us STOPPED.
> > 
> > Well, stuff like this happens when you have lots of users. On the bright side, at least we have users! 
> > Something similar happened when I tried to make emerge --quiet-build the default.
> > 
> > > So, as a result much of the portage team don't feel like working on portage.  Heaven forbid we actually 
> > > make a change!
> > 
> > It's not so bad, considering that you can simply use --dynamic-deps=n if you want, and now --changed-deps 
> > makes it feasible regardless of what ebuild developers do.
> 
> Oops, seems like I stumbled into a delicate area.
> Anyhow, thanks for clarifying this. I will change Transmode defaults to --dynamic-deps=n and
> see what happens.
> Maybe a gentle push for --dynamic-deps=n in the man page could be the way forward?

So I added --dynamic-deps=n and got:
emerge: there are no ebuilds built with USE flags to satisfy ">=virtual/udev-208[gudev]".
!!! One of the following packages is required to complete your request:
- virtual/udev-215::gentoo (Missing IUSE: gudev)
(dependency required by "sys-fs/udisks-2.1.3::gentoo" [installed])
(dependency required by "gnome-base/gvfs-1.20.3::gentoo" [installed]) 
(dependency required by "mate-base/caja-1.8.2-r1::gentoo" [installed]) 
(dependency required by "mate-base/mate-1.8.0::gentoo" [installed]) 
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

After emerge with --changed-deps (165 pkgs), --dynamic-deps=n started to work:)

I guess --dynamic-deps=n found a bug in my database, rebuilding stuff with --changed-deps=y
fixed it.

Then I should use --changed-deps=y with --dynamic-deps=n or is that just extra precaution?

Something else, can I have patches in my profile which epatch_user picks up?

    Jocke

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/11/2015 03:14 PM, Joakim Tjernlund wrote:
> On Wed, 2015-03-11 at 21:02 +0000, Joakim Tjernlund wrote:
>> On Wed, 2015-03-11 at 13:48 -0700, Zac Medico wrote:
>>> On 03/11/2015 01:27 PM, Brian Dolbec wrote:
>>>> On Wed, 11 Mar 2015 20:16:06 +0000
>>>> Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:
>>>>> Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing 
>>>>> something here, an example would be great:)  
>>>>
>>>>
>>>> Because the last time we even discussed the possibility of changing this and steps that might be to fix 
>>>> problems,...  There were a few individuals that raised such a stink about it, they even brought it to 
>>>> council to have us STOPPED.
>>>
>>> Well, stuff like this happens when you have lots of users. On the bright side, at least we have users! 
>>> Something similar happened when I tried to make emerge --quiet-build the default.
>>>
>>>> So, as a result much of the portage team don't feel like working on portage.  Heaven forbid we actually 
>>>> make a change!
>>>
>>> It's not so bad, considering that you can simply use --dynamic-deps=n if you want, and now --changed-deps 
>>> makes it feasible regardless of what ebuild developers do.
>>
>> Oops, seems like I stumbled into a delicate area.
>> Anyhow, thanks for clarifying this. I will change Transmode defaults to --dynamic-deps=n and
>> see what happens.
>> Maybe a gentle push for --dynamic-deps=n in the man page could be the way forward?
> 
> So I added --dynamic-deps=n and got:
> emerge: there are no ebuilds built with USE flags to satisfy ">=virtual/udev-208[gudev]".
> !!! One of the following packages is required to complete your request:
> - virtual/udev-215::gentoo (Missing IUSE: gudev)
> (dependency required by "sys-fs/udisks-2.1.3::gentoo" [installed])
> (dependency required by "gnome-base/gvfs-1.20.3::gentoo" [installed]) 
> (dependency required by "mate-base/caja-1.8.2-r1::gentoo" [installed]) 
> (dependency required by "mate-base/mate-1.8.0::gentoo" [installed]) 
> (dependency required by "@selected" [set])
> (dependency required by "@world" [argument])
> 
> After emerge with --changed-deps (165 pkgs), --dynamic-deps=n started to work:)
> 
> I guess --dynamic-deps=n found a bug in my database, rebuilding stuff with --changed-deps=y
> fixed it.

Yes, this happens when an ebuild developer modifies something important
in an ebuild without doing a revision bump.

> Then I should use --changed-deps=y with --dynamic-deps=n or is that just extra precaution?

Well, if you use --changed-deps together with --newuse, then that will
trigger rebuilds whenever anything interesting changes, which ensures
that --dynamic-deps=n will work just as well as --dynamic-deps=y.

> Something else, can I have patches in my profile which epatch_user picks up?

Looking at the epatch_user code in eutils.eclass, I don't see a way to
for it to interact with your profile. However, your profile can use
profile.bashrc to implement a post_src_prepare hook that applies patches.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/11/2015 01:16 PM, Joakim Tjernlund wrote:
> On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
>> On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
>>> On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
>>>> On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
>>>>> On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
>>>>>>
>>>>>> package.use/package.use.force is a bit different though:
>>>>>> cat /etc/portage/package.use/qemu
>>>>>> app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr virtfs 
>>>>>> static-
>>>>>> user
>>>>>>
>>>>>> #Needed by static-user
>>>>>> sys-libs/zlib static-libs
>>>>>> dev-libs/glib static-libs
>>>>>> sys-apps/attr static-libs
>>>>>>
>>>>>> Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all
>>>>>> flags which has a - on them, emerge wants to turn them on again.
>>>>>>
>>>>>> Am I missing something?
>>>>>> Using portage 2.2.18
>>>>>
>>>>> Appears one have to use package.use.mask for that.
>>>>>  cat package.use.mask
>>>>>  app-emulation/qemu alsa pulseaudio bluetooth opengl
>>>>> It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-alsa -opengl 
>>>>> etc.)
>>>>>
>>>>>  Jocke
>>>>>
>>>>
>>>> Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The negative flags 
>>>> have a
>>>> special meaning within the context of of portage's "incremental stacking" behavior, so they can still 
>>>> be 
>>>> useful, though not in the same way that you you attempted to use them.
>>>
>>>
>>> So now I got to binary pkgs and profiles, the profile is typically part of ebuild src tree/overlay
>>> and a system using only binary pkgs does not need ebuild sources. How does one manage profiles
>>> is this case?
>>> Just sync an empty /usr/portage tree(sans profile) or is the a better way?
>>
>> Recent portage has emerge --sync --sync-submodule=profile, which might be useful. I would like to work 
>> toward handling this case better, so your feedback is welcome.
> 
> That would the same as pointing portage to your own empty tree(sans profile). I was hoping for
> something connected to your BINHOST so one can get all in one go and stored in the same directory
> tree.

Yeah, I'll have to think about that. Maybe we could include a profile
URI in the header of the Packages file.

>>
>>>
>>>  Jocke
>>>
>>> PS.
>>>     emerge --depclean refuses to clean a system which is lagging behind, would it be possible for
>>>     --depclean to go ahead anyway somehow? --dynamic-deps=n comes to mind.
>>
>> You should probably put --dynamic-deps=n in EMERGE_DEFAULT_OPTS, since this option 
>> typically causes these kinds of problems with --depclean. You don't need --dynamic-deps if you use --
>> changed-deps when updating.
> 
> If I do --dynamic-deps=n then man emerge suggest to also do fixpackages(I guess after every SYNC)
> which feels a bit heavy, is this still needed?

Not really, because package moves are applied automatically after each
emerge --sync. This happens unconditionally since FEATURES=fixpackages
was removed [1], unless you use the emerge --package-moves=n option, in
which case we assume that you will manage the consequences yourself.

> Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing
> something here, an example would be great:)  

It's a legacy behavior, since portage has always behaved this way, and
ebuild developers have relied upon it (resulting in broken dependency
calculations without it).

> Will --depclean with --dynamic-deps=n always succeed? I realize that it could be dangerous but
> sometimes would like to have the option.

For the most part, yes. However, you may need to use --with-bdeps=y for
updates, in order to avoid dependency breakage for build-time-only
dependencies.

> BTW, this text is hard to parse:
> --binpkg-changed-deps [ y | n ]
>               Tells  emerge  to ignore binary packages for which the corresponding ebuild depen‐
>               dencies have changed since the packages were built.  In order to help avoid issues
>               with  resolving  inconsistent  dependencies,  this option is automatically enabled
>               unless the --usepkgonly option  is  enabled.  Behavior  with  respect  to  changed
>               build-time dependencies is controlled by the --with-bdeps option.
> 
> --binpkg-changed-deps=y -> Ignore bin pkgs with changed deps?

Yeah, well it's not always easy to translate what the code does into
human language.

[1]
https://github.com/gentoo/portage/commit/7ab4d5722a828167dd1bf946b26cfa80808f59fc
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

> 
> > Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing
> > something here, an example would be great:)  
> 
> It's a legacy behavior, since portage has always behaved this way, and ebuild developers have relied upon 
> it (resulting in broken dependency calculations without it).

Here is odd difference:

emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources
...
   Nothing to merge

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/12/2015 02:43 PM, Joakim Tjernlund wrote:
> 
> 
> 
>>
>>> Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing
>>> something here, an example would be great:)  
>>
>> It's a legacy behavior, since portage has always behaved this way, and ebuild developers have relied upon 
>> it (resulting in broken dependency calculations without it).
> 
> Here is odd difference:
> 
> emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources
> ...
>    Nothing to merge
> 

That's normal, because --changed-deps implies --selective (a number of
options do this). If you add --selective=n to the above command, you'll
get the same result regardless of the --changed-deps option.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Thu, 2015-03-12 at 17:51 -0700, Zac Medico wrote:
> On 03/12/2015 02:43 PM, Joakim Tjernlund wrote:
> > 
> > 
> > 
> > > 
> > > > Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing
> > > > something here, an example would be great:)  
> > > 
> > > It's a legacy behavior, since portage has always behaved this way, and ebuild developers have relied 
> > > upon 
> > > it (resulting in broken dependency calculations without it).
> > 
> > Here is odd difference:
> > 
> > emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources
> > ...
> >    Nothing to merge
> > 
> 
> That's normal, because --changed-deps implies --selective (a number of options do this). If you add --
> selective=n to the above command, you'll get the same result regardless of the --changed-deps option.

Thanks, now it works as before.
Is there something else I should look out for? Behaviour that has changed?

 Jocke

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Thu, 2015-03-12 at 17:51 -0700, Zac Medico wrote:
> On 03/12/2015 02:43 PM, Joakim Tjernlund wrote:
> > 
> > 
> > 
> > > 
> > > > Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing
> > > > something here, an example would be great:)  
> > > 
> > > It's a legacy behavior, since portage has always behaved this way, and ebuild developers have relied 
> > > upon 
> > > it (resulting in broken dependency calculations without it).
> > 
> > Here is odd difference:
> > 
> > emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources
> > ...
> >    Nothing to merge
> > 
> 
> That's normal, because --changed-deps implies --selective (a number of options do this). If you add --
> selective=n to the above command, you'll get the same result regardless of the --changed-deps option.

I just did a sync and "emerge -aNDu --dynamic-deps=n --changed-deps=y --selective=n world" and
again portage wanted to rebuild > 150 pkgs.
--selective=n seems to be the culprit, should I expect this from --selective=n ?

 Jocke

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/13/2015 05:08 AM, Joakim Tjernlund wrote:
> On Thu, 2015-03-12 at 17:51 -0700, Zac Medico wrote:
>> On 03/12/2015 02:43 PM, Joakim Tjernlund wrote:
>>>
>>>
>>>
>>>>
>>>>> Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing
>>>>> something here, an example would be great:)  
>>>>
>>>> It's a legacy behavior, since portage has always behaved this way, and ebuild developers have relied 
>>>> upon 
>>>> it (resulting in broken dependency calculations without it).
>>>
>>> Here is odd difference:
>>>
>>> emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources
>>> ...
>>>    Nothing to merge
>>>
>>
>> That's normal, because --changed-deps implies --selective (a number of options do this). If you add --
>> selective=n to the above command, you'll get the same result regardless of the --changed-deps option.
> 
> I just did a sync and "emerge -aNDu --dynamic-deps=n --changed-deps=y --selective=n world" and
> again portage wanted to rebuild > 150 pkgs.
> --selective=n seems to be the culprit, should I expect this from --selective=n ?

Yes --selective=n is the opposite of --noreplace, so for the above
command, it will rebuild everything in /var/lib/portage/world.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Fri, 2015-03-13 at 10:51 -0700, Zac Medico wrote:
> On 03/13/2015 05:08 AM, Joakim Tjernlund wrote:
> > On Thu, 2015-03-12 at 17:51 -0700, Zac Medico wrote:
> > > On 03/12/2015 02:43 PM, Joakim Tjernlund wrote:
> > > > 
> > > > 
> > > > 
> > > > > 
> > > > > > Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing
> > > > > > something here, an example would be great:)  
> > > > > 
> > > > > It's a legacy behavior, since portage has always behaved this way, and ebuild developers have 
> > > > > relied 
> > > > > upon 
> > > > > it (resulting in broken dependency calculations without it).
> > > > 
> > > > Here is odd difference:
> > > > 
> > > > emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources
> > > > ...
> > > >    Nothing to merge
> > > > 
> > > 
> > > That's normal, because --changed-deps implies --selective (a number of options do this). If you add --
> > > selective=n to the above command, you'll get the same result regardless of the --changed-deps option.
> > 
> > I just did a sync and "emerge -aNDu --dynamic-deps=n --changed-deps=y --selective=n world" and
> > again portage wanted to rebuild > 150 pkgs.
> > --selective=n seems to be the culprit, should I expect this from --selective=n ?
> 
> Yes --selective=n is the opposite of --noreplace, so for the above command, it will rebuild everything in 
> /var/lib/portage/world.

hmm, this kind of a bummer
--dynamic-deps=n implies --changed-deps=y which implies --selective=n
and this makes the whole world to rebuild.

Using just --dynamic-deps=n was not really safe if I understood corretly?

 Jocke

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/14/2015 05:55 AM, Joakim Tjernlund wrote:
> On Fri, 2015-03-13 at 10:51 -0700, Zac Medico wrote:
>> On 03/13/2015 05:08 AM, Joakim Tjernlund wrote:
>>> On Thu, 2015-03-12 at 17:51 -0700, Zac Medico wrote:
>>>> On 03/12/2015 02:43 PM, Joakim Tjernlund wrote:
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>>> Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably missing
>>>>>>> something here, an example would be great:)  
>>>>>>
>>>>>> It's a legacy behavior, since portage has always behaved this way, and ebuild developers have 
>>>>>> relied 
>>>>>> upon 
>>>>>> it (resulting in broken dependency calculations without it).
>>>>>
>>>>> Here is odd difference:
>>>>>
>>>>> emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources
>>>>> ...
>>>>>    Nothing to merge
>>>>>
>>>>
>>>> That's normal, because --changed-deps implies --selective (a number of options do this). If you add --
>>>> selective=n to the above command, you'll get the same result regardless of the --changed-deps option.
>>>
>>> I just did a sync and "emerge -aNDu --dynamic-deps=n --changed-deps=y --selective=n world" and
>>> again portage wanted to rebuild > 150 pkgs.
>>> --selective=n seems to be the culprit, should I expect this from --selective=n ?
>>
>> Yes --selective=n is the opposite of --noreplace, so for the above command, it will rebuild everything in 
>> /var/lib/portage/world.
> 
> hmm, this kind of a bummer

I don't understand your motivation for using --selective=n with that
command. Isn't the command useful without it?

> --dynamic-deps=n implies --changed-deps=y which implies --selective=n
> and this makes the whole world to rebuild.

No, don't use --selective=n. I only mentioned it in order to explain the
behavior that you observed.

> Using just --dynamic-deps=n was not really safe if I understood corretly?

It's safe, but you may need --changed-deps in order for your dependency
calculations to work (depends on how the dependencies of your installed
packages have changed).
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Sat, 2015-03-14 at 10:58 -0700, Zac Medico wrote:
> On 03/14/2015 05:55 AM, Joakim Tjernlund wrote:
> > On Fri, 2015-03-13 at 10:51 -0700, Zac Medico wrote:
> > > On 03/13/2015 05:08 AM, Joakim Tjernlund wrote:
> > > > On Thu, 2015-03-12 at 17:51 -0700, Zac Medico wrote:
> > > > > On 03/12/2015 02:43 PM, Joakim Tjernlund wrote:
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > > 
> > > > > > > > Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably 
> > > > > > > > missing
> > > > > > > > something here, an example would be great:)  
> > > > > > > 
> > > > > > > It's a legacy behavior, since portage has always behaved this way, and ebuild developers have 
> > > > > > > relied 
> > > > > > > upon 
> > > > > > > it (resulting in broken dependency calculations without it).
> > > > > > 
> > > > > > Here is odd difference:
> > > > > > 
> > > > > > emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources
> > > > > > ...
> > > > > >    Nothing to merge
> > > > > > 
> > > > > 
> > > > > That's normal, because --changed-deps implies --selective (a number of options do this). If you add 
> > > > > --
> > > > > selective=n to the above command, you'll get the same result regardless of the --changed-deps 
> > > > > option.
> > > > 
> > > > I just did a sync and "emerge -aNDu --dynamic-deps=n --changed-deps=y --selective=n world" and
> > > > again portage wanted to rebuild > 150 pkgs.
> > > > --selective=n seems to be the culprit, should I expect this from --selective=n ?
> > > 
> > > Yes --selective=n is the opposite of --noreplace, so for the above command, it will rebuild everything 
> > > in 
> > > /var/lib/portage/world.
> > 
> > hmm, this kind of a bummer
> 
> I don't understand your motivation for using --selective=n with that command. Isn't the command useful 
> without it?

I have it my default emerge options 

> 
> > --dynamic-deps=n implies --changed-deps=y which implies --selective=n
> > and this makes the whole world to rebuild.
> 
> No, don't use --selective=n. I only mentioned it in order to explain the behavior that you observed.
> 
> > Using just --dynamic-deps=n was not really safe if I understood corretly?
> 
> It's safe, but you may need --changed-deps in order for your dependency calculations to work (depends on 
> how the dependencies of your installed packages have changed).

I am trying to find out what to put in emerge default options and this "may need"
does relay compute in terms of default options.
Does --dynamic-deps=n only work reliable with emerge -NDu world ?

 Jocke

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/14/2015 11:35 AM, Joakim Tjernlund wrote:
> On Sat, 2015-03-14 at 10:58 -0700, Zac Medico wrote:
>> On 03/14/2015 05:55 AM, Joakim Tjernlund wrote:
>>> On Fri, 2015-03-13 at 10:51 -0700, Zac Medico wrote:
>>>> On 03/13/2015 05:08 AM, Joakim Tjernlund wrote:
>>>>> On Thu, 2015-03-12 at 17:51 -0700, Zac Medico wrote:
>>>>>> On 03/12/2015 02:43 PM, Joakim Tjernlund wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>> Why is --dynamic-deps=y default? This feels like lying about your true deps, I am probably 
>>>>>>>>> missing
>>>>>>>>> something here, an example would be great:)  
>>>>>>>>
>>>>>>>> It's a legacy behavior, since portage has always behaved this way, and ebuild developers have 
>>>>>>>> relied 
>>>>>>>> upon 
>>>>>>>> it (resulting in broken dependency calculations without it).
>>>>>>>
>>>>>>> Here is odd difference:
>>>>>>>
>>>>>>> emerge --dynamic-deps=n changed-deps=y -a1 vanilla-sources
>>>>>>> ...
>>>>>>>    Nothing to merge
>>>>>>>
>>>>>>
>>>>>> That's normal, because --changed-deps implies --selective (a number of options do this). If you add 
>>>>>> --
>>>>>> selective=n to the above command, you'll get the same result regardless of the --changed-deps 
>>>>>> option.
>>>>>
>>>>> I just did a sync and "emerge -aNDu --dynamic-deps=n --changed-deps=y --selective=n world" and
>>>>> again portage wanted to rebuild > 150 pkgs.
>>>>> --selective=n seems to be the culprit, should I expect this from --selective=n ?
>>>>
>>>> Yes --selective=n is the opposite of --noreplace, so for the above command, it will rebuild everything 
>>>> in 
>>>> /var/lib/portage/world.
>>>
>>> hmm, this kind of a bummer
>>
>> I don't understand your motivation for using --selective=n with that command. Isn't the command useful 
>> without it?
> 
> I have it my default emerge options 
> 
>>
>>> --dynamic-deps=n implies --changed-deps=y which implies --selective=n
>>> and this makes the whole world to rebuild.
>>
>> No, don't use --selective=n. I only mentioned it in order to explain the behavior that you observed.
>>
>>> Using just --dynamic-deps=n was not really safe if I understood corretly?
>>
>> It's safe, but you may need --changed-deps in order for your dependency calculations to work (depends on 
>> how the dependencies of your installed packages have changed).
> 
> I am trying to find out what to put in emerge default options and this "may need"
> does relay compute in terms of default options.

Right, options that imply --selective are not well suited for
EMERGE_DEFAULT_OPTS unless you also put --selective=n in
EMERGE_DEFAULT_OPTS, and then use --selective just for the commands that
require it.

As an alternative, we can add support for command-specific default
options, as discussed here:

https://bugs.gentoo.org/show_bug.cgi?id=540250#c1

> Does --dynamic-deps=n only work reliable with emerge -NDu world ?

No, it's well suited for EMERGE_DEFAULT_OPTS. It's just that you may
find that you encounter dependency conflicts for some calculations
unless you use --changed-deps. I use --changed-deps for all of my world
updates.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Wed, 2015-03-11 at 13:43 -0700, Zac Medico wrote:
> On 03/11/2015 01:16 PM, Joakim Tjernlund wrote:
> > On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
> > > On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
> > > > On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
> > > > > On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
> > > > > > On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
> > > > > > > 
> > > > > > > package.use/package.use.force is a bit different though:
> > > > > > > cat /etc/portage/package.use/qemu
> > > > > > > app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr 
> > > > > > > virtfs 
> > > > > > > static-
> > > > > > > user
> > > > > > > 
> > > > > > > #Needed by static-user
> > > > > > > sys-libs/zlib static-libs
> > > > > > > dev-libs/glib static-libs
> > > > > > > sys-apps/attr static-libs
> > > > > > > 
> > > > > > > Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all
> > > > > > > flags which has a - on them, emerge wants to turn them on again.
> > > > > > > 
> > > > > > > Am I missing something?
> > > > > > > Using portage 2.2.18
> > > > > > 
> > > > > > Appears one have to use package.use.mask for that.
> > > > > >  cat package.use.mask
> > > > > >  app-emulation/qemu alsa pulseaudio bluetooth opengl
> > > > > > It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-alsa -
> > > > > > opengl 
> > > > > > etc.)
> > > > > > 
> > > > > >  Jocke
> > > > > > 
> > > > > 
> > > > > Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The negative 
> > > > > flags 
> > > > > have a
> > > > > special meaning within the context of of portage's "incremental stacking" behavior, so they can 
> > > > > still 
> > > > > be 
> > > > > useful, though not in the same way that you you attempted to use them.

Just noticed that USE flags in profiles/package.use.mask override everything so this
  USE=thin emerge -av sys-fs/lvm2
will not turn on thin if thin is in profiles/package.use.mask
How can just change the default so a user can easily turn it on ?

 jcoke 

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/14/2015 09:12 AM, Joakim Tjernlund wrote:
> On Wed, 2015-03-11 at 13:43 -0700, Zac Medico wrote:
>> On 03/11/2015 01:16 PM, Joakim Tjernlund wrote:
>>> On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
>>>> On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
>>>>> On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
>>>>>> On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
>>>>>>> On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
>>>>>>>>
>>>>>>>> package.use/package.use.force is a bit different though:
>>>>>>>> cat /etc/portage/package.use/qemu
>>>>>>>> app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr 
>>>>>>>> virtfs 
>>>>>>>> static-
>>>>>>>> user
>>>>>>>>
>>>>>>>> #Needed by static-user
>>>>>>>> sys-libs/zlib static-libs
>>>>>>>> dev-libs/glib static-libs
>>>>>>>> sys-apps/attr static-libs
>>>>>>>>
>>>>>>>> Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl all
>>>>>>>> flags which has a - on them, emerge wants to turn them on again.
>>>>>>>>
>>>>>>>> Am I missing something?
>>>>>>>> Using portage 2.2.18
>>>>>>>
>>>>>>> Appears one have to use package.use.mask for that.
>>>>>>>  cat package.use.mask
>>>>>>>  app-emulation/qemu alsa pulseaudio bluetooth opengl
>>>>>>> It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-alsa -
>>>>>>> opengl 
>>>>>>> etc.)
>>>>>>>
>>>>>>>  Jocke
>>>>>>>
>>>>>>
>>>>>> Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The negative 
>>>>>> flags 
>>>>>> have a
>>>>>> special meaning within the context of of portage's "incremental stacking" behavior, so they can 
>>>>>> still 
>>>>>> be 
>>>>>> useful, though not in the same way that you you attempted to use them.
> 
> Just noticed that USE flags in profiles/package.use.mask override everything so this
>   USE=thin emerge -av sys-fs/lvm2
> will not turn on thin if thin is in profiles/package.use.mask
> How can just change the default so a user can easily turn it on ?

Generally, setting the USE environment variable like that is poor
practice, because the setting will not persist the next time that you
rebuild the package. So, you should set the flag in
/etc/portage/package.use. You can unmask the flag for lvm2 like this:

  echo "sys-fs/lvm2 -thin" >> /etc/portage/profile/package.use.mask

Or umask it globally like this:

  echo -thin >> /etc/portage/profile/use.mask

-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Sat, 2015-03-14 at 11:08 -0700, Zac Medico wrote:
> On 03/14/2015 09:12 AM, Joakim Tjernlund wrote:
> > On Wed, 2015-03-11 at 13:43 -0700, Zac Medico wrote:
> > > On 03/11/2015 01:16 PM, Joakim Tjernlund wrote:
> > > > On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
> > > > > On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
> > > > > > On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
> > > > > > > On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
> > > > > > > > On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
> > > > > > > > > 
> > > > > > > > > package.use/package.use.force is a bit different though:
> > > > > > > > > cat /etc/portage/package.use/qemu
> > > > > > > > > app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr 
> > > > > > > > > virtfs 
> > > > > > > > > static-
> > > > > > > > > user
> > > > > > > > > 
> > > > > > > > > #Needed by static-user
> > > > > > > > > sys-libs/zlib static-libs
> > > > > > > > > dev-libs/glib static-libs
> > > > > > > > > sys-apps/attr static-libs
> > > > > > > > > 
> > > > > > > > > Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl 
> > > > > > > > > all
> > > > > > > > > flags which has a - on them, emerge wants to turn them on again.
> > > > > > > > > 
> > > > > > > > > Am I missing something?
> > > > > > > > > Using portage 2.2.18
> > > > > > > > 
> > > > > > > > Appears one have to use package.use.mask for that.
> > > > > > > >  cat package.use.mask
> > > > > > > >  app-emulation/qemu alsa pulseaudio bluetooth opengl
> > > > > > > > It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-alsa -
> > > > > > > > opengl 
> > > > > > > > etc.)
> > > > > > > > 
> > > > > > > >  Jocke
> > > > > > > > 
> > > > > > > 
> > > > > > > Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The negative 
> > > > > > > flags 
> > > > > > > have a
> > > > > > > special meaning within the context of of portage's "incremental stacking" behavior, so they can 
> > > > > > > still 
> > > > > > > be 
> > > > > > > useful, though not in the same way that you you attempted to use them.
> > 
> > Just noticed that USE flags in profiles/package.use.mask override everything so this
> >   USE=thin emerge -av sys-fs/lvm2
> > will not turn on thin if thin is in profiles/package.use.mask
> > How can just change the default so a user can easily turn it on ?
> 
> Generally, setting the USE environment variable like that is poor practice, because the setting will not 
> persist the next time that you rebuild the package. So, you should set the flag in 


I know, this was just an example to illustrate that it did not work.

> /etc/portage/package.use. You can unmask the flag for lvm2 like this:
> 
>   echo "sys-fs/lvm2 -thin" >> /etc/portage/profile/package.use.mask

You misunderstand, I have "sys-fs/lvm2 thin" in /etc/portage/profile/package.use.mask
and I want a user to able to override this setting, using USE=".." or adding it
to their local /etc/portage/package.use file/dir

> 
> Or umask it globally like this:
> 
>   echo -thin >> /etc/portage/profile/use.mask
> 

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/14/2015 11:41 AM, Joakim Tjernlund wrote:
> On Sat, 2015-03-14 at 11:08 -0700, Zac Medico wrote:
>> On 03/14/2015 09:12 AM, Joakim Tjernlund wrote:
>>> On Wed, 2015-03-11 at 13:43 -0700, Zac Medico wrote:
>>>> On 03/11/2015 01:16 PM, Joakim Tjernlund wrote:
>>>>> On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
>>>>>> On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
>>>>>>> On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
>>>>>>>> On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
>>>>>>>>> On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
>>>>>>>>>>
>>>>>>>>>> package.use/package.use.force is a bit different though:
>>>>>>>>>> cat /etc/portage/package.use/qemu
>>>>>>>>>> app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 xattr 
>>>>>>>>>> virtfs 
>>>>>>>>>> static-
>>>>>>>>>> user
>>>>>>>>>>
>>>>>>>>>> #Needed by static-user
>>>>>>>>>> sys-libs/zlib static-libs
>>>>>>>>>> dev-libs/glib static-libs
>>>>>>>>>> sys-apps/attr static-libs
>>>>>>>>>>
>>>>>>>>>> Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -opengl 
>>>>>>>>>> all
>>>>>>>>>> flags which has a - on them, emerge wants to turn them on again.
>>>>>>>>>>
>>>>>>>>>> Am I missing something?
>>>>>>>>>> Using portage 2.2.18
>>>>>>>>>
>>>>>>>>> Appears one have to use package.use.mask for that.
>>>>>>>>>  cat package.use.mask
>>>>>>>>>  app-emulation/qemu alsa pulseaudio bluetooth opengl
>>>>>>>>> It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-alsa -
>>>>>>>>> opengl 
>>>>>>>>> etc.)
>>>>>>>>>
>>>>>>>>>  Jocke
>>>>>>>>>
>>>>>>>>
>>>>>>>> Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The negative 
>>>>>>>> flags 
>>>>>>>> have a
>>>>>>>> special meaning within the context of of portage's "incremental stacking" behavior, so they can 
>>>>>>>> still 
>>>>>>>> be 
>>>>>>>> useful, though not in the same way that you you attempted to use them.
>>>
>>> Just noticed that USE flags in profiles/package.use.mask override everything so this
>>>   USE=thin emerge -av sys-fs/lvm2
>>> will not turn on thin if thin is in profiles/package.use.mask
>>> How can just change the default so a user can easily turn it on ?
>>
>> Generally, setting the USE environment variable like that is poor practice, because the setting will not 
>> persist the next time that you rebuild the package. So, you should set the flag in 
> 
> 
> I know, this was just an example to illustrate that it did not work.
> 
>> /etc/portage/package.use. You can unmask the flag for lvm2 like this:
>>
>>   echo "sys-fs/lvm2 -thin" >> /etc/portage/profile/package.use.mask
> 
> You misunderstand, I have "sys-fs/lvm2 thin" in /etc/portage/profile/package.use.mask
> and I want a user to able to override this setting, using USE=".." or adding it
> to their local /etc/portage/package.use file/dir

There's no other way to negate a use mask than to use
/etc/portage/profile/{use.mask,package.use.mask} as I have described. I
don't think that it makes much sense to negate a use mask for a single
emerge invocation. If you want to do that, then why is the use flag
masked anyway?
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Sat, 2015-03-14 at 11:57 -0700, Zac Medico wrote:
> On 03/14/2015 11:41 AM, Joakim Tjernlund wrote:
> > On Sat, 2015-03-14 at 11:08 -0700, Zac Medico wrote:
> > > On 03/14/2015 09:12 AM, Joakim Tjernlund wrote:
> > > > On Wed, 2015-03-11 at 13:43 -0700, Zac Medico wrote:
> > > > > On 03/11/2015 01:16 PM, Joakim Tjernlund wrote:
> > > > > > On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
> > > > > > > On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
> > > > > > > > On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
> > > > > > > > > On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
> > > > > > > > > > On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
> > > > > > > > > > > 
> > > > > > > > > > > package.use/package.use.force is a bit different though:
> > > > > > > > > > > cat /etc/portage/package.use/qemu
> > > > > > > > > > > app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 
> > > > > > > > > > > xattr 
> > > > > > > > > > > virtfs 
> > > > > > > > > > > static-
> > > > > > > > > > > user
> > > > > > > > > > > 
> > > > > > > > > > > #Needed by static-user
> > > > > > > > > > > sys-libs/zlib static-libs
> > > > > > > > > > > dev-libs/glib static-libs
> > > > > > > > > > > sys-apps/attr static-libs
> > > > > > > > > > > 
> > > > > > > > > > > Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -
> > > > > > > > > > > opengl 
> > > > > > > > > > > all
> > > > > > > > > > > flags which has a - on them, emerge wants to turn them on again.
> > > > > > > > > > > 
> > > > > > > > > > > Am I missing something?
> > > > > > > > > > > Using portage 2.2.18
> > > > > > > > > > 
> > > > > > > > > > Appears one have to use package.use.mask for that.
> > > > > > > > > >  cat package.use.mask
> > > > > > > > > >  app-emulation/qemu alsa pulseaudio bluetooth opengl
> > > > > > > > > > It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-
> > > > > > > > > > alsa -
> > > > > > > > > > opengl 
> > > > > > > > > > etc.)
> > > > > > > > > > 
> > > > > > > > > >  Jocke
> > > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The 
> > > > > > > > > negative 
> > > > > > > > > flags 
> > > > > > > > > have a
> > > > > > > > > special meaning within the context of of portage's "incremental stacking" behavior, so they 
> > > > > > > > > can 
> > > > > > > > > still 
> > > > > > > > > be 
> > > > > > > > > useful, though not in the same way that you you attempted to use them.
> > > > 
> > > > Just noticed that USE flags in profiles/package.use.mask override everything so this
> > > >   USE=thin emerge -av sys-fs/lvm2
> > > > will not turn on thin if thin is in profiles/package.use.mask
> > > > How can just change the default so a user can easily turn it on ?
> > > 
> > > Generally, setting the USE environment variable like that is poor practice, because the setting will 
> > > not 
> > > persist the next time that you rebuild the package. So, you should set the flag in 
> > 
> > 
> > I know, this was just an example to illustrate that it did not work.
> > 
> > > /etc/portage/package.use. You can unmask the flag for lvm2 like this:
> > > 
> > >   echo "sys-fs/lvm2 -thin" >> /etc/portage/profile/package.use.mask
> > 
> > You misunderstand, I have "sys-fs/lvm2 thin" in /etc/portage/profile/package.use.mask
> > and I want a user to able to override this setting, using USE=".." or adding it
> > to their local /etc/portage/package.use file/dir
> 
> There's no other way to negate a use mask than to use /etc/portage/profile/{use.mask,package.use.mask} as I 
> have described. I don't think that it makes much sense to negate a use mask for a single emerge invocation. 
> If you want to do that, then why is the use flag masked anyway?

I am putting tougher a profile for my company where I want to specify default
USE flags for different apps/libs. Then a user who knows what he/she is doing
should be able to override these defaults. It is not possible as far
as I can tell to override negative USE flags or is there?

     Jocke

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/14/2015 12:30 PM, Joakim Tjernlund wrote:
> On Sat, 2015-03-14 at 11:57 -0700, Zac Medico wrote:
>> On 03/14/2015 11:41 AM, Joakim Tjernlund wrote:
>>> On Sat, 2015-03-14 at 11:08 -0700, Zac Medico wrote:
>>>> On 03/14/2015 09:12 AM, Joakim Tjernlund wrote:
>>>>> On Wed, 2015-03-11 at 13:43 -0700, Zac Medico wrote:
>>>>>> On 03/11/2015 01:16 PM, Joakim Tjernlund wrote:
>>>>>>> On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
>>>>>>>> On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
>>>>>>>>> On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
>>>>>>>>>> On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
>>>>>>>>>>> On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> package.use/package.use.force is a bit different though:
>>>>>>>>>>>> cat /etc/portage/package.use/qemu
>>>>>>>>>>>> app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl qemu_user_targets_x86_64 
>>>>>>>>>>>> xattr 
>>>>>>>>>>>> virtfs 
>>>>>>>>>>>> static-
>>>>>>>>>>>> user
>>>>>>>>>>>>
>>>>>>>>>>>> #Needed by static-user
>>>>>>>>>>>> sys-libs/zlib static-libs
>>>>>>>>>>>> dev-libs/glib static-libs
>>>>>>>>>>>> sys-apps/attr static-libs
>>>>>>>>>>>>
>>>>>>>>>>>> Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -
>>>>>>>>>>>> opengl 
>>>>>>>>>>>> all
>>>>>>>>>>>> flags which has a - on them, emerge wants to turn them on again.
>>>>>>>>>>>>
>>>>>>>>>>>> Am I missing something?
>>>>>>>>>>>> Using portage 2.2.18
>>>>>>>>>>>
>>>>>>>>>>> Appears one have to use package.use.mask for that.
>>>>>>>>>>>  cat package.use.mask
>>>>>>>>>>>  app-emulation/qemu alsa pulseaudio bluetooth opengl
>>>>>>>>>>> It would be handy if one could use the same syntax as in /etc/portage/package.use/qemu(-
>>>>>>>>>>> alsa -
>>>>>>>>>>> opengl 
>>>>>>>>>>> etc.)
>>>>>>>>>>>
>>>>>>>>>>>  Jocke
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The 
>>>>>>>>>> negative 
>>>>>>>>>> flags 
>>>>>>>>>> have a
>>>>>>>>>> special meaning within the context of of portage's "incremental stacking" behavior, so they 
>>>>>>>>>> can 
>>>>>>>>>> still 
>>>>>>>>>> be 
>>>>>>>>>> useful, though not in the same way that you you attempted to use them.
>>>>>
>>>>> Just noticed that USE flags in profiles/package.use.mask override everything so this
>>>>>   USE=thin emerge -av sys-fs/lvm2
>>>>> will not turn on thin if thin is in profiles/package.use.mask
>>>>> How can just change the default so a user can easily turn it on ?
>>>>
>>>> Generally, setting the USE environment variable like that is poor practice, because the setting will 
>>>> not 
>>>> persist the next time that you rebuild the package. So, you should set the flag in 
>>>
>>>
>>> I know, this was just an example to illustrate that it did not work.
>>>
>>>> /etc/portage/package.use. You can unmask the flag for lvm2 like this:
>>>>
>>>>   echo "sys-fs/lvm2 -thin" >> /etc/portage/profile/package.use.mask
>>>
>>> You misunderstand, I have "sys-fs/lvm2 thin" in /etc/portage/profile/package.use.mask
>>> and I want a user to able to override this setting, using USE=".." or adding it
>>> to their local /etc/portage/package.use file/dir
>>
>> There's no other way to negate a use mask than to use /etc/portage/profile/{use.mask,package.use.mask} as I 
>> have described. I don't think that it makes much sense to negate a use mask for a single emerge invocation. 
>> If you want to do that, then why is the use flag masked anyway?
> 
> I am putting tougher a profile for my company where I want to specify default
> USE flags for different apps/libs. Then a user who knows what he/she is doing
> should be able to override these defaults. It is not possible as far
> as I can tell to override negative USE flags or is there?

You can set default USE flags in the profile, and then the users can
override those settings locally (both positively and negatively). You
should not be using use.mask at all here. The profile can set
USE="-flag" in make.defaults, or in packages.use, and the user can
override that without having to mess with use.mask.
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Sat, 2015-03-14 at 14:02 -0700, Zac Medico wrote:
> On 03/14/2015 12:30 PM, Joakim Tjernlund wrote:
> > On Sat, 2015-03-14 at 11:57 -0700, Zac Medico wrote:
> > > On 03/14/2015 11:41 AM, Joakim Tjernlund wrote:
> > > > On Sat, 2015-03-14 at 11:08 -0700, Zac Medico wrote:
> > > > > On 03/14/2015 09:12 AM, Joakim Tjernlund wrote:
> > > > > > On Wed, 2015-03-11 at 13:43 -0700, Zac Medico wrote:
> > > > > > > On 03/11/2015 01:16 PM, Joakim Tjernlund wrote:
> > > > > > > > On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
> > > > > > > > > On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
> > > > > > > > > > On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
> > > > > > > > > > > On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
> > > > > > > > > > > > On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
> > > > > > > > > > > > > 
> > > > > > > > > > > > > package.use/package.use.force is a bit different though:
> > > > > > > > > > > > > cat /etc/portage/package.use/qemu
> > > > > > > > > > > > > app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl 
> > > > > > > > > > > > > qemu_user_targets_x86_64 
> > > > > > > > > > > > > xattr 
> > > > > > > > > > > > > virtfs 
> > > > > > > > > > > > > static-
> > > > > > > > > > > > > user
> > > > > > > > > > > > > 
> > > > > > > > > > > > > #Needed by static-user
> > > > > > > > > > > > > sys-libs/zlib static-libs
> > > > > > > > > > > > > dev-libs/glib static-libs
> > > > > > > > > > > > > sys-apps/attr static-libs
> > > > > > > > > > > > > 
> > > > > > > > > > > > > Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, -
> > > > > > > > > > > > > opengl 
> > > > > > > > > > > > > all
> > > > > > > > > > > > > flags which has a - on them, emerge wants to turn them on again.
> > > > > > > > > > > > > 
> > > > > > > > > > > > > Am I missing something?
> > > > > > > > > > > > > Using portage 2.2.18
> > > > > > > > > > > > 
> > > > > > > > > > > > Appears one have to use package.use.mask for that.
> > > > > > > > > > > >  cat package.use.mask
> > > > > > > > > > > >  app-emulation/qemu alsa pulseaudio bluetooth opengl
> > > > > > > > > > > > It would be handy if one could use the same syntax as in 
> > > > > > > > > > > > /etc/portage/package.use/qemu(-
> > > > > > > > > > > > alsa -
> > > > > > > > > > > > opengl 
> > > > > > > > > > > > etc.)
> > > > > > > > > > > > 
> > > > > > > > > > > >  Jocke
> > > > > > > > > > > > 
> > > > > > > > > > > 
> > > > > > > > > > > Yes, the inverted use.mask logic can be confusing if you are not familiar with it. The 
> > > > > > > > > > > negative 
> > > > > > > > > > > flags 
> > > > > > > > > > > have a
> > > > > > > > > > > special meaning within the context of of portage's "incremental stacking" behavior, so 
> > > > > > > > > > > they 
> > > > > > > > > > > can 
> > > > > > > > > > > still 
> > > > > > > > > > > be 
> > > > > > > > > > > useful, though not in the same way that you you attempted to use them.
> > > > > > 
> > > > > > Just noticed that USE flags in profiles/package.use.mask override everything so this
> > > > > >   USE=thin emerge -av sys-fs/lvm2
> > > > > > will not turn on thin if thin is in profiles/package.use.mask
> > > > > > How can just change the default so a user can easily turn it on ?
> > > > > 
> > > > > Generally, setting the USE environment variable like that is poor practice, because the setting 
> > > > > will 
> > > > > not 
> > > > > persist the next time that you rebuild the package. So, you should set the flag in 
> > > > 
> > > > 
> > > > I know, this was just an example to illustrate that it did not work.
> > > > 
> > > > > /etc/portage/package.use. You can unmask the flag for lvm2 like this:
> > > > > 
> > > > >   echo "sys-fs/lvm2 -thin" >> /etc/portage/profile/package.use.mask
> > > > 
> > > > You misunderstand, I have "sys-fs/lvm2 thin" in /etc/portage/profile/package.use.mask
> > > > and I want a user to able to override this setting, using USE=".." or adding it
> > > > to their local /etc/portage/package.use file/dir
> > > 
> > > There's no other way to negate a use mask than to use /etc/portage/profile/{use.mask,package.use.mask} 
> > > as I 
> > > have described. I don't think that it makes much sense to negate a use mask for a single emerge 
> > > invocation. 
> > > If you want to do that, then why is the use flag masked anyway?
> > 
> > I am putting tougher a profile for my company where I want to specify default
> > USE flags for different apps/libs. Then a user who knows what he/she is doing
> > should be able to override these defaults. It is not possible as far as I can tell to override negative 
> > USE flags or is there?
> 
> You can set default USE flags in the profile, and then the users can override those settings locally (both 
> positively and negatively). You should not be using use.mask at all here. The profile can set USE="-flag" 
> in make.defaults, or in packages.use, and the user can override that without having to mess with use.mask.

That is how I started, I added -thin etc. to profile's package.use and it didn't work so I moved over
to package.mask.
Now when I try with -thin again in profile's package.use it actually works!
I have no idea what got wrong the first time.
Anyhow, thank you for your patience. I will continue moving over all
Transmode stuff to our new profile the next few days :)

 Jocke 

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Sun, 2015-03-15 at 16:37 +0000, Joakim Tjernlund wrote:
> On Sat, 2015-03-14 at 14:02 -0700, Zac Medico wrote:
> > On 03/14/2015 12:30 PM, Joakim Tjernlund wrote:
> > > On Sat, 2015-03-14 at 11:57 -0700, Zac Medico wrote:
> > > > On 03/14/2015 11:41 AM, Joakim Tjernlund wrote:
> > > > > On Sat, 2015-03-14 at 11:08 -0700, Zac Medico wrote:
> > > > > > On 03/14/2015 09:12 AM, Joakim Tjernlund wrote:
> > > > > > > On Wed, 2015-03-11 at 13:43 -0700, Zac Medico wrote:
> > > > > > > > On 03/11/2015 01:16 PM, Joakim Tjernlund wrote:
> > > > > > > > > On Wed, 2015-03-11 at 10:56 -0700, Zac Medico wrote:
> > > > > > > > > > On 03/11/2015 08:48 AM, Joakim Tjernlund wrote:
> > > > > > > > > > > On Sun, 2015-03-08 at 11:58 -0700, Zac Medico wrote:
> > > > > > > > > > > > On 03/08/2015 10:01 AM, Joakim Tjernlund wrote:
> > > > > > > > > > > > > On Sun, 2015-03-08 at 15:47 +0000, Joakim Tjernlund wrote:
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > package.use/package.use.force is a bit different though:
> > > > > > > > > > > > > > cat /etc/portage/package.use/qemu
> > > > > > > > > > > > > > app-emulation/qemu vde -alsa -pulseaudio -bluetooth -opengl  
> > > > > > > > > > > > > > qemu_user_targets_x86_64 
> > > > > > > > > > > > > > xattr 
> > > > > > > > > > > > > > virtfs 
> > > > > > > > > > > > > > static-
> > > > > > > > > > > > > > user
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > #Needed by static-user
> > > > > > > > > > > > > > sys-libs/zlib static-libs
> > > > > > > > > > > > > > dev-libs/glib static-libs
> > > > > > > > > > > > > > sys-apps/attr static-libs
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > Moving this to package.use/package.use.force does not respect -alsa, -pulseaudio, 
> > > > > > > > > > > > > > -
> > > > > > > > > > > > > > opengl 
> > > > > > > > > > > > > > all
> > > > > > > > > > > > > > flags which has a - on them, emerge wants to turn them on again.
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > Am I missing something?
> > > > > > > > > > > > > > Using portage 2.2.18
> > > > > > > > > > > > > 
> > > > > > > > > > > > > Appears one have to use package.use.mask for that.
> > > > > > > > > > > > >  cat package.use.mask
> > > > > > > > > > > > >  app-emulation/qemu alsa pulseaudio bluetooth opengl
> > > > > > > > > > > > > It would be handy if one could use the same syntax as in 
> > > > > > > > > > > > > /etc/portage/package.use/qemu(-
> > > > > > > > > > > > > alsa -
> > > > > > > > > > > > > opengl 
> > > > > > > > > > > > > etc.)
> > > > > > > > > > > > > 
> > > > > > > > > > > > >  Jocke
> > > > > > > > > > > > > 
> > > > > > > > > > > > 
> > > > > > > > > > > > Yes, the inverted use.mask logic can be confusing if you are not familiar with it. 
> > > > > > > > > > > > The 
> > > > > > > > > > > > negative 
> > > > > > > > > > > > flags 
> > > > > > > > > > > > have a
> > > > > > > > > > > > special meaning within the context of of portage's "incremental stacking" behavior, 
> > > > > > > > > > > > so 
> > > > > > > > > > > > they 
> > > > > > > > > > > > can 
> > > > > > > > > > > > still 
> > > > > > > > > > > > be 
> > > > > > > > > > > > useful, though not in the same way that you you attempted to use them.
> > > > > > > 
> > > > > > > Just noticed that USE flags in profiles/package.use.mask override everything so this
> > > > > > >   USE=thin emerge -av sys-fs/lvm2
> > > > > > > will not turn on thin if thin is in profiles/package.use.mask
> > > > > > > How can just change the default so a user can easily turn it on ?
> > > > > > 
> > > > > > Generally, setting the USE environment variable like that is poor practice, because the setting 
> > > > > > will 
> > > > > > not 
> > > > > > persist the next time that you rebuild the package. So, you should set the flag in 
> > > > > 
> > > > > 
> > > > > I know, this was just an example to illustrate that it did not work.
> > > > > 
> > > > > > /etc/portage/package.use. You can unmask the flag for lvm2 like this:
> > > > > > 
> > > > > >   echo "sys-fs/lvm2 -thin" >> /etc/portage/profile/package.use.mask
> > > > > 
> > > > > You misunderstand, I have "sys-fs/lvm2 thin" in /etc/portage/profile/package.use.mask
> > > > > and I want a user to able to override this setting, using USE=".." or adding it
> > > > > to their local /etc/portage/package.use file/dir
> > > > 
> > > > There's no other way to negate a use mask than to use 
> > > > /etc/portage/profile/{use.mask,package.use.mask} 
> > > > as I 
> > > > have described. I don't think that it makes much sense to negate a use mask for a single emerge 
> > > > invocation. 
> > > > If you want to do that, then why is the use flag masked anyway?
> > > 
> > > I am putting tougher a profile for my company where I want to specify default
> > > USE flags for different apps/libs. Then a user who knows what he/she is doing
> > > should be able to override these defaults. It is not possible as far as I can tell to override negative 
> > > USE flags or is there?
> > 
> > You can set default USE flags in the profile, and then the users can override those settings locally 
> > (both 
> > positively and negatively). You should not be using use.mask at all here. The profile can set USE="-flag" 
> > in make.defaults, or in packages.use, and the user can override that without having to mess with use.mask.
> 
> That is how I started, I added -thin etc. to profile's package.use and it didn't work so I moved over
> to package.mask.
> Now when I try with -thin again in profile's package.use it actually works!
> I have no idea what got wrong the first time.
> Anyhow, thank you for your patience. I will continue moving over all Transmode stuff to our new profile the 
> next few days :)

hmm, spoke too fast. Negative USE flags in profiles package.use works on other
computers but mine :-(

I have in profiles package.use:
 app-emulation/qemu usb usbredir vde qemu_user_targets_x86_64 xattr virtfs static-user -alsa -pulseaudio -bluetooth -opengl
but on my computer the -USE flags(-alsa -pulseaudio -bluetooth -opengl) have no effect.
I have been looking high and low what could case this but no luck, any pointers ? 

 Jocke

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 03/16/2015 09:31 AM, Joakim Tjernlund wrote:
> On Sun, 2015-03-15 at 16:37 +0000, Joakim Tjernlund wrote:
>> On Sat, 2015-03-14 at 14:02 -0700, Zac Medico wrote:
>>>
>>> You can set default USE flags in the profile, and then the users can override those settings locally 
>>> (both 
>>> positively and negatively). You should not be using use.mask at all here. The profile can set USE="-flag" 
>>> in make.defaults, or in packages.use, and the user can override that without having to mess with use.mask.
>>
>> That is how I started, I added -thin etc. to profile's package.use and it didn't work so I moved over
>> to package.mask.
>> Now when I try with -thin again in profile's package.use it actually works!
>> I have no idea what got wrong the first time.
>> Anyhow, thank you for your patience. I will continue moving over all Transmode stuff to our new profile the 
>> next few days :)
> 
> hmm, spoke too fast. Negative USE flags in profiles package.use works on other
> computers but mine :-(
> 
> I have in profiles package.use:
>  app-emulation/qemu usb usbredir vde qemu_user_targets_x86_64 xattr virtfs static-user -alsa -pulseaudio -bluetooth -opengl
> but on my computer the -USE flags(-alsa -pulseaudio -bluetooth -opengl) have no effect.
> I have been looking high and low what could case this but no luck, any pointers ? 

Maybe you have overridden the default USE_ORDER setting? You can use
this command to check it:

   portageq envvar USE_ORDER

-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Mon, 2015-03-16 at 11:12 -0700, Zac Medico wrote:
> On 03/16/2015 09:31 AM, Joakim Tjernlund wrote:
> > On Sun, 2015-03-15 at 16:37 +0000, Joakim Tjernlund wrote:
> > > On Sat, 2015-03-14 at 14:02 -0700, Zac Medico wrote:
> > > > 
> > > > You can set default USE flags in the profile, and then the users can override those settings locally 
> > > > (both 
> > > > positively and negatively). You should not be using use.mask at all here. The profile can set USE="-
> > > > flag" 
> > > > in make.defaults, or in packages.use, and the user can override that without having to mess with 
> > > > use.mask.
> > > 
> > > That is how I started, I added -thin etc. to profile's package.use and it didn't work so I moved over
> > > to package.mask.
> > > Now when I try with -thin again in profile's package.use it actually works!
> > > I have no idea what got wrong the first time.
> > > Anyhow, thank you for your patience. I will continue moving over all Transmode stuff to our new profile 
> > > the 
> > > next few days :)
> > 
> > hmm, spoke too fast. Negative USE flags in profiles package.use works on other
> > computers but mine :-(
> > 
> > I have in profiles package.use:
> >  app-emulation/qemu usb usbredir vde qemu_user_targets_x86_64 xattr virtfs static-user -alsa -pulseaudio -
> > bluetooth -opengl
> > but on my computer the -USE flags(-alsa -pulseaudio -bluetooth -opengl) have no effect.
> > I have been looking high and low what could case this but no luck, any pointers ? 
> 
> Maybe you have overridden the default USE_ORDER setting? You can use
> this command to check it:
> 
>    portageq envvar USE_ORDER
> 

That was not it, however:
It seems like USE in /etc/portage/make.conf overrides any negative
USE flags in profiles/package.use ?
Example
 /etc/portage/make.conf: USE=alsa
 .../profiles/package.use: app-emulation/qemu -alsa
Here USE=alsa overides app-emulation/qemu -alsa ?

Seems asymmetric that you can only add but not subtract USE flags
in profiles/package.use. 

 Jocke

Re: [gentoo-portage-dev] custom profiles?

[Zac Medico]

On 04/01/2015 02:00 PM, Joakim Tjernlund wrote:
> On Mon, 2015-03-16 at 11:12 -0700, Zac Medico wrote:
>> On 03/16/2015 09:31 AM, Joakim Tjernlund wrote:
>>> On Sun, 2015-03-15 at 16:37 +0000, Joakim Tjernlund wrote:
>>>> On Sat, 2015-03-14 at 14:02 -0700, Zac Medico wrote:
>>>>>
>>>>> You can set default USE flags in the profile, and then the users can override those settings locally 
>>>>> (both 
>>>>> positively and negatively). You should not be using use.mask at all here. The profile can set USE="-
>>>>> flag" 
>>>>> in make.defaults, or in packages.use, and the user can override that without having to mess with 
>>>>> use.mask.
>>>>
>>>> That is how I started, I added -thin etc. to profile's package.use and it didn't work so I moved over
>>>> to package.mask.
>>>> Now when I try with -thin again in profile's package.use it actually works!
>>>> I have no idea what got wrong the first time.
>>>> Anyhow, thank you for your patience. I will continue moving over all Transmode stuff to our new profile 
>>>> the 
>>>> next few days :)
>>>
>>> hmm, spoke too fast. Negative USE flags in profiles package.use works on other
>>> computers but mine :-(
>>>
>>> I have in profiles package.use:
>>>  app-emulation/qemu usb usbredir vde qemu_user_targets_x86_64 xattr virtfs static-user -alsa -pulseaudio -
>>> bluetooth -opengl
>>> but on my computer the -USE flags(-alsa -pulseaudio -bluetooth -opengl) have no effect.
>>> I have been looking high and low what could case this but no luck, any pointers ? 
>>
>> Maybe you have overridden the default USE_ORDER setting? You can use
>> this command to check it:
>>
>>    portageq envvar USE_ORDER
>>
> 
> That was not it, however:
> It seems like USE in /etc/portage/make.conf overrides any negative
> USE flags in profiles/package.use ?

Yes, this is a direct result of the default
USE_ORDER="env:pkg:conf:defaults:pkginternal:repo:env.d" setting. Since
"conf" comes before "defaults", make.conf overrides make.defaults. This
allows local user settings to override profile settings, which should be
intuitive for most people (I think).

> Example
>  /etc/portage/make.conf: USE=alsa
>  .../profiles/package.use: app-emulation/qemu -alsa
> Here USE=alsa overides app-emulation/qemu -alsa ?
> 
> Seems asymmetric that you can only add but not subtract USE flags
> in profiles/package.use. 

You can also subtract them, but it only works for settings that occurred
earlier in the profile's make.defaults, in IUSE defaults, or in env.d (a
direct result of the default USE_ORDER setting).
-- 
Thanks,
Zac

Re: [gentoo-portage-dev] custom profiles?

[Joakim Tjernlund]

On Wed, 2015-04-01 at 14:28 -0700, Zac Medico wrote:
> On 04/01/2015 02:00 PM, Joakim Tjernlund wrote:
> > On Mon, 2015-03-16 at 11:12 -0700, Zac Medico wrote:
> > > On 03/16/2015 09:31 AM, Joakim Tjernlund wrote:
> > > > On Sun, 2015-03-15 at 16:37 +0000, Joakim Tjernlund wrote:
> > > > > On Sat, 2015-03-14 at 14:02 -0700, Zac Medico wrote:
> > > > > > 
> > > > > > You can set default USE flags in the profile, and then the users can override those settings 
> > > > > > locally 
> > > > > > (both 
> > > > > > positively and negatively). You should not be using use.mask at all here. The profile can set 
> > > > > > USE="-
> > > > > > flag" 
> > > > > > in make.defaults, or in packages.use, and the user can override that without having to mess with 
> > > > > > use.mask.
> > > > > 
> > > > > That is how I started, I added -thin etc. to profile's package.use and it didn't work so I moved 
> > > > > over
> > > > > to package.mask.
> > > > > Now when I try with -thin again in profile's package.use it actually works!
> > > > > I have no idea what got wrong the first time.
> > > > > Anyhow, thank you for your patience. I will continue moving over all Transmode stuff to our new 
> > > > > profile 
> > > > > the 
> > > > > next few days :)
> > > > 
> > > > hmm, spoke too fast. Negative USE flags in profiles package.use works on other
> > > > computers but mine :-(
> > > > 
> > > > I have in profiles package.use:
> > > >  app-emulation/qemu usb usbredir vde qemu_user_targets_x86_64 xattr virtfs static-user -alsa -
> > > > pulseaudio -
> > > > bluetooth -opengl
> > > > but on my computer the -USE flags(-alsa -pulseaudio -bluetooth -opengl) have no effect.
> > > > I have been looking high and low what could case this but no luck, any pointers ? 
> > > 
> > > Maybe you have overridden the default USE_ORDER setting? You can use
> > > this command to check it:
> > > 
> > >    portageq envvar USE_ORDER
> > > 
> > 
> > That was not it, however:
> > It seems like USE in /etc/portage/make.conf overrides any negative
> > USE flags in profiles/package.use ?
> 
> Yes, this is a direct result of the default
> USE_ORDER="env:pkg:conf:defaults:pkginternal:repo:env.d" setting. Since
> "conf" comes before "defaults", make.conf overrides make.defaults. This
> allows local user settings to override profile settings, which should be
> intuitive for most people (I think).

For make.conf vs make.defaults yes but I am talking about package.use
I figured any USE setting in package.use for a specific pkg would override
any general USE setting in make.conf or make.defaults.
For package.use in /etc/portage this is true but not for 
package.use located in the profile.

> 
> > Example
> >  /etc/portage/make.conf: USE=alsa
> >  .../profiles/package.use: app-emulation/qemu -alsa
> > Here USE=alsa overides app-emulation/qemu -alsa ?
> > 
> > Seems asymmetric that you can only add but not subtract USE flags
> > in profiles/package.use. 
> 
> You can also subtract them, but it only works for settings that occurred
> earlier in the profile's make.defaults, in IUSE defaults, or in env.d (a
> direct result of the default USE_ORDER setting).

No, I can not subtract USE flags in profile/package.use if the same
flag is present in make.conf

 Jocke