On Monday, 31 October 2022 23:06:18 GMT Neil Bothwick wrote:
> On Mon, 31 Oct 2022 22:32:34 +0100, Arve Barsnes wrote:
> > On Mon, 31 Oct 2022 at 22:12, Walter Dnes <walt...@waltdnes.org
> > > On Sat, Oct 29, 2022 at 11:39:47PM +0100, Neil Bothwick wrote
> > >
> > > > qlist -IC | grep -e x11-base -e x11-apps -e x11-fonts
> > > >
> > > > >/etc/portage/sets/x11 emerge -n @x11
> > > >
> > > > Saves filling @world with dozens of x11 entries.
> > > >
> > > 1) Has /var/lib/portage/set_name been deprecated?
> > No. The new default is now /var/lib/portage. Check your
> > /etc/portage/repos.conf/gentoo.conf if you're in doubt about where
> > your main repo is.
> When did that happen? The portage man page still shows /etc/portage/sets/
> as the location for user-defined sets.
There seems to be some confusion here. /var/lib/portage is where portage
stores things; /etc/portage is where you store portage things.
> > > 2) Will items in /etc/portage/sets/<whatever> be automatically
> > > updated each time you update world?
> Provided the set is in world_sets, all packages in it will be treated as
> if they were in @world for updates.
In my case, nearly all the packages I want installed are specified in 6 sets in
/etc/portage/sets/<set-name>. When I emerge one of those sets, portage adds it
to /var/lib/portage/world_sets, just as any package I emerge specifically goes
into /var/lib/portage/world. In fact my world file has just three entries at
the moment: things I'm trying before they're moved to a set.
Neat and tidy.
This scheme may seem backwards; I started it when I was going through a great
many reinstallations and wanted to go methodically, one step at a time. First
a core set, then a broader base set, then xorg, plasma and apps. The
appropriate profile would be set for each stage. I'd set up the kernel config
after the core, so that the rest of the base packages had proper kernel
settings to read. That gave me a bootable system and I'd finish the job in the
new system itself.