diff options
author | V3n3RiX <venerix@redcorelinux.org> | 2021-10-01 20:54:53 +0100 |
---|---|---|
committer | V3n3RiX <venerix@redcorelinux.org> | 2021-10-01 20:54:53 +0100 |
commit | 391b5b359a346aff490103da7dddc85047f83830 (patch) | |
tree | 29eea460a0bd7e1ff21d43b9d6df9af4d8a175e1 /profiles/default | |
parent | c719fdcee603a5a706a45d10cb598762d56a727d (diff) |
gentoo resync : 01.10.2021
Diffstat (limited to 'profiles/default')
5 files changed, 215 insertions, 0 deletions
diff --git a/profiles/default/linux/riscv/17.0/rv64gc/deprecated b/profiles/default/linux/riscv/17.0/rv64gc/deprecated new file mode 100644 index 000000000000..36128fb4712c --- /dev/null +++ b/profiles/default/linux/riscv/17.0/rv64gc/deprecated @@ -0,0 +1,43 @@ +default/linux/riscv/20.0/rv64gc/lp64d + +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. diff --git a/profiles/default/linux/riscv/17.0/rv64gc/lp64/deprecated b/profiles/default/linux/riscv/17.0/rv64gc/lp64/deprecated new file mode 100644 index 000000000000..e38047556647 --- /dev/null +++ b/profiles/default/linux/riscv/17.0/rv64gc/lp64/deprecated @@ -0,0 +1,43 @@ +default/linux/riscv/20.0/rv64gc/lp64 + +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. diff --git a/profiles/default/linux/riscv/17.0/rv64gc/lp64/systemd/deprecated b/profiles/default/linux/riscv/17.0/rv64gc/lp64/systemd/deprecated new file mode 100644 index 000000000000..70e347cc4398 --- /dev/null +++ b/profiles/default/linux/riscv/17.0/rv64gc/lp64/systemd/deprecated @@ -0,0 +1,43 @@ +default/linux/riscv/20.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. diff --git a/profiles/default/linux/riscv/17.0/rv64gc/lp64d/deprecated b/profiles/default/linux/riscv/17.0/rv64gc/lp64d/deprecated new file mode 100644 index 000000000000..36128fb4712c --- /dev/null +++ b/profiles/default/linux/riscv/17.0/rv64gc/lp64d/deprecated @@ -0,0 +1,43 @@ +default/linux/riscv/20.0/rv64gc/lp64d + +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. diff --git a/profiles/default/linux/riscv/17.0/rv64gc/lp64d/systemd/deprecated b/profiles/default/linux/riscv/17.0/rv64gc/lp64d/systemd/deprecated new file mode 100644 index 000000000000..cbac179df32e --- /dev/null +++ b/profiles/default/linux/riscv/17.0/rv64gc/lp64d/systemd/deprecated @@ -0,0 +1,43 @@ +default/linux/riscv/20.0/rv64gc/lp64d/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. |