From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: New profiles 23.0
Date: Tue, 26 Mar 2024 20:16:59 -0000 (UTC) [thread overview]
Message-ID: <utvafr$o2u$1@ciao.gmane.io> (raw)
In-Reply-To: MTAwMDAyMi53ZG5lc2RheQ.1711482945@quikprotect
On 2024-03-26, Walter Dnes <waltdnes@waltdnes.org> wrote:
> On Tue, Mar 26, 2024 at 04:21:23PM +0000, Michael wrote
>> On Tuesday, 26 March 2024 15:21:32 GMT Walter Dnes wrote:
>> > I assume my system is already "merged-usr". Current profile...
>> >
>> > [12] default/linux/amd64/17.1/no-multilib (exp) *
>> >
[...]
>
> Thanks for the clarification. So my system is considered
> "split-usr", regardless of everything being on one partition.
Yes. "split user" means that /bin and /usr/bin are two different
directories. Likewise for /lib and /usr/lib, and so on...
It doesn't matter that /foo and /usr/foo directories are in the same
filesystem.
> I got the news item when I ran "emerge --sync". My understanding is
> that step 1 in the news item says "Please also update your system
> fully and depclean before proceeding" so I should update world
> first.
Yes. And depclean.
> Since I'm currently on profile
> "default/linux/amd64/17.1/no-multilib" then I should migrate to
> profile "default/linux/amd64/23.0/split-usr/no-multilib" as per the
> news item.
Yes -- If you're using OpenRC. I assume you are not using systemd
since your old profile wasn't a systemd profile [In theory you could
be running systemd on a non-systemd profile, but it's not common.] If
you are running systemd, you should first update to the "merged-usr"
flavor of your current profile.
There's a detailed table at
https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
It shows exactly what new profile corresponds to what old profile.
> Migrating from there to "default/linux/amd64/23.0/no-multilib" is a
> separate process as per the Gentoo wiki. Is my understanding
> correct?
Yes: https://wiki.gentoo.org/wiki/Merge-usr
next prev parent reply other threads:[~2024-03-26 20:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 14:59 [gentoo-user] New profiles 23.0 Peter Humphrey
2024-03-23 15:08 ` Peter Humphrey
2024-03-23 16:56 ` Michael
2024-03-23 16:56 ` Peter Humphrey
2024-03-23 17:33 ` Dale
2024-03-23 17:42 ` Michael
2024-03-23 18:29 ` ralfconn
2024-03-23 18:43 ` Michael
[not found] ` <bc051c33-92ed-4eee-812a-2e85e7c3d9f5@yahoo.com>
[not found] ` <3741700.MHq7AAxBmi@rogueboard>
2024-03-23 19:37 ` ralfconn
2024-03-24 15:50 ` ralfconn
2024-03-23 19:38 ` Dale
2024-03-25 14:41 ` Peter Humphrey
2024-03-25 17:00 ` Jacques Montier
2024-03-25 17:17 ` Michael
2024-03-25 17:37 ` Jacques Montier
2024-03-25 17:44 ` Michael
2024-03-25 18:54 ` Jacques Montier
2024-03-26 10:32 ` William KENWORTHY
2024-03-26 13:01 ` Michael
2024-03-29 17:46 ` Michael
2024-03-24 18:31 ` Björn Fischer
2024-03-24 18:34 ` Michael
2024-03-26 15:21 ` Walter Dnes
2024-03-26 15:27 ` Walter Dnes
2024-03-26 15:35 ` Peter Humphrey
2024-03-26 15:51 ` [gentoo-user] " Grant Edwards
2024-03-26 16:21 ` [gentoo-user] " Michael
2024-03-26 19:55 ` Walter Dnes
2024-03-26 20:16 ` Grant Edwards [this message]
2024-03-30 18:34 ` [gentoo-user] " Walter Dnes
2024-04-02 18:54 ` J. Roeleveld
2024-03-26 17:13 ` [gentoo-user] " Dale
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='utvafr$o2u$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--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