On 20/11/2016 02:43, Harry Putnam wrote: > > [...] > > Neil Bothwick <n...@digimed.co.uk> 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 <alan.mckin...@gmail.com> 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
