Joakim Tjernlund posted on Tue, 24 Nov 2015 17:24:19 +0000 as excerpted:
> I have created my own set, @cusfpv3, and now I want to include this set
> in @world using my custom profile.
> How can I do that?
>
> I can add it in overlay/sets.conf:
> [CUSFPv3 sets]
> class = portage.sets.files.StaticFileSet
> multiset = true
> directory =
> %(PORTAGE_CONFIGROOT)s${repository:tmv3-target-overlay}/sets/
>
> [world]
> class = portage.sets.base.DummyPackageSet
> packages = @cusfpv3 @profile @selected @system
>
> But then this set becomes active as soon as one add the overlay to a
> machine and I do not want that.
You don't need the set in sets.conf, only in the world_sets file,
/var/lib/portage/world_sets , with the set file itself then in
/etc/portage/sets .
FWIW, my world file (/var/lib/portage/world) is normally entirely empty.
Instead, I have everything that would normally be listed there, listed in
various sets in /etc/portage/sets/*. These are organized by functional
category.
So the world_sets file contains entries like:
@jed.admin
@jed.fonts
@jed.kde.kde-baseapps
@jed.media
...
(JED are my initials. Here, they're used so I can distinguish on sight
my own sets from others, for instance the kde-baseapps sets found in the
kde overlay.)
Then for example the /etc/portage/sets/jed.fonts file:
media-fonts/dejavu
media-fonts/freefont
media-fonts/font-adobe-100dpi
media-fonts/font-bh-100dpi
media-fonts/font-bh-lucidatypewriter-100dpi
media-fonts/font-bitstream-100dpi
media-fonts/font-ibm-type1
But I do occasionally use my world file as a sort of "package purgatory"
for packages I haven't decided for sure whether I want to keep or not,
but still want to protect them from depclean. If I decide to keep them,
they're moved to the appropriate sets file. If not, I simply delete the
entry in world and let depclean do its thing.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
