[gentoo-user] Re: `sets' & sets.conf

2016-11-20 Thread Harry Putnam
Neil Bothwick  writes:

> On Sat, 19 Nov 2016 19:43:56 -0500, Harry Putnam wrote:
>
>> > % cat /etc/portage/sets.conf
>> > [kernels]
>> > class = portage.sets.dbapi.OwnerSet
>> > world-candidate = False
>> > files = /usr/src
>> >
>> > then emerge -n @kernels  
>> 
>> This one kind of sails right over my head... not seeing what is
>> supposed to happen.
>
> It's in the part of my post you didn't quote, it stops older kernels
> being depcleaned. Basically it is saying that any package with files
> in /usr/src is a member of the kernels set. As emerge -n @kernels adds
> that to world_sets, nothing with files in /usr/src will even get
> depcleaned. It means I can keep as many or as few kernels as I want
> without having to fudge it in world.

Got it thanks again... can't really apologize for the densness factor
but I guess my punishment is ... I live with it...




Re: [gentoo-user] Re: `sets' & sets.conf

2016-11-20 Thread Neil Bothwick
On Sat, 19 Nov 2016 19:43:56 -0500, Harry Putnam wrote:

> > % cat /etc/portage/sets.conf
> > [kernels]
> > class = portage.sets.dbapi.OwnerSet
> > world-candidate = False
> > files = /usr/src
> >
> > then emerge -n @kernels  
> 
> This one kind of sails right over my head... not seeing what is
> supposed to happen.

It's in the part of my post you didn't quote, it stops older kernels
being depcleaned. Basically it is saying that any package with files
in /usr/src is a member of the kernels set. As emerge -n @kernels adds
that to world_sets, nothing with files in /usr/src will even get
depcleaned. It means I can keep as many or as few kernels as I want
without having to fudge it in world.


-- 
Neil Bothwick

And if you say "No", I shall be forced to shoot you.


pgphc59PHx1bo.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Re: `sets' & sets.conf

2016-11-19 Thread Alan McKinnon
On 20/11/2016 02:43, Harry Putnam wrote:
> 
> [...]
> 
> Neil Bothwick  writes:
> 
>> You can create a set containing a list of packages. I do this for
>> dependencies of packages that are not from portage, so they don't get
>> depcleaned and don't end up in @world. Something like
> 
> [...]
> Thanks for the nifty examples... ... missing entirely in the pile of
> documenation at /usr/share/doc/portage-2.3.2/html/index.html
> (if you have USE=doc set)
> 
>> % cat /etc/portage/sets.conf
>> [kernels]
>> class = portage.sets.dbapi.OwnerSet
>> world-candidate = False
>> files = /usr/src
>>
>> then emerge -n @kernels
> 
> This one kind of sails right over my head... not seeing what is
> supposed to happen.
> 
> [...]
> 
> Alan McKinnon  writes:
> 
> [...]
> 
>> Think of it as sort of like a magic meta-package that you define - a set
>> gets merged as a unit and where you unmerge it, the sets is out of world
>> and depclean will take care of removing the members.
>>
>> Simple as that.  I'm not aware of anything in FEATURES related to sets,
>> you just use them out the box.
> 
> Gack, I was following along OK until the part about `out of the box'
> 
> Do you mean those toxic looking definitions or other stuff in the docs
> at /usr/share/doc/portage-2.3.2/html/index.html? ...
> 
> 


No, I mean:

install portage
vi /etc/portage/sets/mystuff
emerge @mystuff


-- 
Alan McKinnon
alan.mckin...@gmail.com




[gentoo-user] Re: `sets' & sets.conf

2016-11-19 Thread Harry Putnam

[...]

Neil Bothwick  writes:

> You can create a set containing a list of packages. I do this for
> dependencies of packages that are not from portage, so they don't get
> depcleaned and don't end up in @world. Something like

[...]
Thanks for the nifty examples... ... missing entirely in the pile of
documenation at /usr/share/doc/portage-2.3.2/html/index.html
(if you have USE=doc set)

> % cat /etc/portage/sets.conf
> [kernels]
> class = portage.sets.dbapi.OwnerSet
> world-candidate = False
> files = /usr/src
>
> then emerge -n @kernels

This one kind of sails right over my head... not seeing what is
supposed to happen.

[...]

Alan McKinnon  writes:

[...]

> Think of it as sort of like a magic meta-package that you define - a set
> gets merged as a unit and where you unmerge it, the sets is out of world
> and depclean will take care of removing the members.
>
> Simple as that.  I'm not aware of anything in FEATURES related to sets,
> you just use them out the box.

Gack, I was following along OK until the part about `out of the box'

Do you mean those toxic looking definitions or other stuff in the docs
at /usr/share/doc/portage-2.3.2/html/index.html? ...