From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] x11-bas/xorg-x11 removal
Date: Mon, 31 Oct 2022 23:06:18 +0000 [thread overview]
Message-ID: <20221031230618.4cb3f6d4@digimed.co.uk> (raw)
In-Reply-To: <CAJjrzcWTzYdtq6MNiddcMB+ukiAWThhJNjg-kakX4duOOrJL0w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
On Mon, 31 Oct 2022 22:32:34 +0100, Arve Barsnes wrote:
> On Mon, 31 Oct 2022 at 22:12, Walter Dnes <waltdnes@waltdnes.org> wrote:
> >
> > 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.
> > 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.
--
Neil Bothwick
Guns don't kill people--it's those little pieces of lead.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-31 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5bd4da44-49a4-972a-e75b-5258093a6839.ref@yahoo.com>
2022-10-29 8:26 ` [gentoo-user] x11-bas/xorg-x11 removal ralfconn
2022-10-29 10:09 ` David Haller
2022-10-29 10:47 ` ralfconn
2022-10-29 22:39 ` Neil Bothwick
2022-10-31 21:12 ` Walter Dnes
2022-10-31 21:32 ` Arve Barsnes
2022-10-31 23:06 ` Neil Bothwick [this message]
2022-11-01 8:44 ` Peter Humphrey
2022-11-01 9:58 ` Arve Barsnes
2022-11-01 15:14 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221031230618.4cb3f6d4@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox