From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: pr@gentoo.org
Subject: [gentoo-dev] news item: riscv upgrade to 20.0 profiles
Date: Sat, 19 Jun 2021 23:04:06 +0200 [thread overview]
Message-ID: <4829068.M3retTD8dW@pinacolada> (raw)
[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]
Feedback welcome...
Title: riscv upgrade to 20.0 profiles
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Posted: 2021-06-25
Revision: 1
News-Item-Format: 2.0
Display-If-Profile: default/linux/riscv/17.0/rv64gc/lp64d
Display-If-Profile: default/linux/riscv/17.0/rv64gc/lp64d/systemd
Display-If-Profile: default/linux/riscv/17.0/rv64gc/lp64
Display-If-Profile: default/linux/riscv/17.0/rv64gc/lp64/systemd
On RISC-V we are switching from two-level library directories (e.g.,
/usr/lib64/lp64d) to a more traditional directory architecture.
This is done via the profile upgrade from 17.0 to 20.0 profiles.
We recommend to re-install from scratch using a 20.0 profile based
stage. 17.0 profiles will be deprecated immediately and removed
in 6 months.
If you want to upgrade an existing installation, the following
steps should be taken. Please read all commands carefully first and
make sure you understand them, since the procedure is risky. The
commands are given for a lp64d profile; in case of a lp64 profile,
always replace lp64d with lp64.
# cd /usr/local/lib64
# cp -av lp64d/. .
# rm -rf lp64d
# ln -s . lp64d
# cd /usr/lib64
# cp -av lp64d/. .
# rm -rf lp64d
# ln -s . lp64d
# cd /lib64
# cp -av lp64d/. .
# rm -rf lp64d
# sln . lp64d
Note that the last command uses "sln" instead of "ln -s".
Then switch from your 17.0 profile to the corresponding 20.0 profile,
either by using "eselect profile" or by manually changing the
/etc/portage/make.profile symlink.
Next, rebuild all packages:
# emerge -eav world
As last step, check if portage has removed any of the symlinks created
above, and if yes, recreate them.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
reply other threads:[~2021-06-19 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4829068.M3retTD8dW@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@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