mirror of
https://github.com/flatcar/scripts.git
synced 2025-09-27 16:41:11 +02:00
profiles: Sync with Gentoo
It's from Gentoo commit f328287a62cf11e026aa92c853557c8c8bafddf6.
This commit is contained in:
Flatcar Buildbot
Mathieu Tortuyaux
parent
637f6dd3fe
commit
d8f50c18cd
@ -1,6 +1,14 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-29)
|
||||
# media-libs/libplacebo is not keyworded
|
||||
media-video/ffmpeg libplacebo
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-05-08)
|
||||
# Requires sys-devel/{clang,llvm}:16.
|
||||
dev-lang/python jit
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2024-02-29)
|
||||
# sys-apps/xdg-desktop-portal is not keyworded here, #925731
|
||||
x11-base/xwayland libei
|
||||
@ -205,7 +213,6 @@ sci-libs/umfpack cholmod
|
||||
media-libs/openal sndio
|
||||
media-video/ffmpeg sndio
|
||||
media-sound/moc sndio
|
||||
media-sound/mpd sndio
|
||||
media-libs/libsdl2 sndio
|
||||
media-libs/libao sndio
|
||||
|
||||
@ -246,7 +253,7 @@ mail-filter/pyzor mysql
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2020-08-11)
|
||||
# No drivers on this architecture support Vulkan
|
||||
media-libs/mesa vulkan vulkan-overlay zink
|
||||
media-libs/mesa video_cards_zink vulkan vulkan-overlay zink
|
||||
|
||||
# Sergei Trofimovich <slyfox@gentoo.org> (2020-07-18)
|
||||
# net-libs/webkit-gtk has no alpha keywords
|
||||
@ -331,10 +338,6 @@ dev-db/percona-server cjk
|
||||
app-admin/sudo sssd
|
||||
sys-auth/pambase sssd
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2018-09-30)
|
||||
# Optional dependency blocking security cleanup, bug #627316
|
||||
media-sound/mpd wildmidi
|
||||
|
||||
# Thomas Deutschmann <whissi@gentoo.org> (2018-06-06)
|
||||
# Needs sys-apps/fakechroot which isn't keyworded
|
||||
app-arch/rpm test
|
||||
@ -499,10 +502,6 @@ media-video/ffmpeg x265
|
||||
# Missing keywords, bug #493156
|
||||
media-libs/libgphoto2 serial
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-11-28)
|
||||
# Missing keywords, bug #492820
|
||||
net-im/telepathy-connection-managers sipe
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-11-13)
|
||||
# Missing keywords, bug #478254
|
||||
>=gnome-base/gnome-3.8 classic
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
ARCH="amd64"
|
||||
|
||||
@ -5,10 +5,6 @@
|
||||
# This code assumes 32-bit longs and must therefore be built as a 32-bit binary.
|
||||
sys-fs/atari-fdisk
|
||||
|
||||
# David Seifert <soap@gentoo.org> (2018-01-03)
|
||||
# Requires 32-bit multilib compatibility
|
||||
sys-block/megamgr
|
||||
|
||||
# James Le Cuirot <chewi@gentoo.org> (2016-08-13)
|
||||
# Steam requires amd64 multilib. These are steam-overlay packages.
|
||||
dev-util/adobe-air-runtime
|
||||
@ -27,7 +23,6 @@ app-emulation/crossover-bin
|
||||
app-emulation/q4wine
|
||||
dev-embedded/libftd2xx
|
||||
dev-embedded/openocd
|
||||
dev-util/android-ndk
|
||||
dev-util/android-sdk-update-manager
|
||||
dev-util/biew
|
||||
games-action/badland
|
||||
|
||||
@ -17,9 +17,21 @@
|
||||
|
||||
#--- END OF EXAMPLES ---
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-23)
|
||||
# Pulls in kde-apps/kgpg is keyworded here
|
||||
>=kde-apps/kdeutils-meta-24.05.1 -gpg
|
||||
|
||||
# Jared Allard <jared@rgst.io> (2024-06-21)
|
||||
# uasm and jwasm include amd64-specific ASM
|
||||
app-arch/7zip -uasm -jwasm
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-04-25)
|
||||
# ROCm and Level-Zero are amd64-only at the moment
|
||||
sys-apps/hwloc -rocm -l0
|
||||
|
||||
# Paul Zander <negril.nx+gentoo@gmail.com> (2024-04-20)
|
||||
# only keyworded for amd64 currently
|
||||
media-gfx/blender -gnome
|
||||
media-gfx/blender -gnome -oneapi -renderdoc -vulkan
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-04-16)
|
||||
# dev-qt/qtlanguageserver:6 is keyworded here
|
||||
@ -75,11 +87,6 @@ sys-kernel/gentoo-kernel-bin -generic-uki
|
||||
# dev-qt/qtwebengine:6 is keyworded here.
|
||||
dev-python/PyQt6 -pdfium
|
||||
|
||||
# Leonardo Hernández Hernández <leohdz172@proton.me> (2023-11-25)
|
||||
# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff)
|
||||
# are only available for amd64, arm64 and riscv
|
||||
>=gui-libs/wlroots-0.17.0 -drm -liftoff
|
||||
|
||||
# Jimi Huotari <chiitoo@gentoo.org> (2023-11-22)
|
||||
# Unmask on amd64.
|
||||
media-video/obs-studio -qsv -websocket
|
||||
@ -131,6 +138,7 @@ www-servers/apache -apache2_modules_tls
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-04-22)
|
||||
# snap only works on amd64
|
||||
gnome-extra/gnome-software -snap
|
||||
kde-plasma/discover -snap
|
||||
|
||||
# Sam James <sam@gentoo.org> (2023-04-17)
|
||||
@ -142,10 +150,6 @@ dev-lang/ruby -jit
|
||||
# pytables is available here.
|
||||
dev-python/tables -cpudetection
|
||||
|
||||
# Craig Andrews <candrews@gentoo.org> (2023-03-09)
|
||||
# media-libs/libplacebo is keyworded here
|
||||
media-video/ffmpeg -libplacebo
|
||||
|
||||
# Yiyang Wu <xgreenlandforwyy@gmail.com> (2023-01-27)
|
||||
# AMDGPU enablement depends on dev-libs/rocr-runtime, ~amd64 only
|
||||
# See also: https://bugs.gentoo.org/891499
|
||||
@ -168,7 +172,6 @@ net-misc/curl -rustls -curl_ssl_rustls
|
||||
# Quick Sync Video (through intel-mediasdk or libvpl) is
|
||||
# only keyworded on amd64
|
||||
media-video/ffmpeg -qsv
|
||||
media-libs/gst-plugins-bad -qsv
|
||||
|
||||
# WANG Xuerui <xen0n@gentoo.org> (2022-10-07)
|
||||
# sys-libs/libsmbios is available here.
|
||||
@ -246,6 +249,7 @@ sys-libs/compiler-rt-sanitizers -asan -dfsan -lsan -msan -hwasan -tsan
|
||||
sys-libs/compiler-rt-sanitizers -ubsan -safestack -cfi -scudo
|
||||
sys-libs/compiler-rt-sanitizers -gwp-asan
|
||||
sys-libs/compiler-rt-sanitizers -libfuzzer -memprof -orc -profile -xray
|
||||
sys-libs/compiler-rt-sanitizers -ctx-profile
|
||||
|
||||
# Sam James <sam@gentoo.org> (2020-10-24)
|
||||
# asm redc is only available on amd64,
|
||||
@ -325,10 +329,6 @@ dev-java/openjdk:11 -javafx
|
||||
# build on amd64.
|
||||
>=dev-lang/spidermonkey-60 -jit
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2019-05-09)
|
||||
# media-libs/libplacebo is keyworded on amd64
|
||||
media-video/vlc -libplacebo
|
||||
|
||||
# Denis Lisov <dennis.lissov@gmail.com> (2019-05-09)
|
||||
# Overlay can only be built on amd64 and x86
|
||||
x11-apps/igt-gpu-tools -overlay
|
||||
|
||||
@ -17,11 +17,6 @@
|
||||
|
||||
#--- END OF EXAMPLES ---
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-04-16)
|
||||
# Temporary mask to give a little bit of time before stabilizing
|
||||
# the just added dev-qt/qtlanguageserver-6.7.0 for amd64
|
||||
dev-qt/qtdeclarative:6 qmlls
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-17)
|
||||
# Experimental, virt-firmware is keyworded only unstable
|
||||
sys-kernel/installkernel efistub
|
||||
@ -75,7 +70,6 @@ net-misc/curl rustls curl_ssl_rustls
|
||||
|
||||
# Sam James <sam@gentoo.org> (2022-12-07)
|
||||
# Needs unstable media-libs/libvpl
|
||||
media-libs/gst-plugins-bad qsv
|
||||
media-video/ffmpeg qsv
|
||||
|
||||
# Adel Kara Slimane <adel.ks@zegrapher.com> (2022-03-14)
|
||||
|
||||
@ -1,6 +1,11 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Ben Kohler <bkohler@gentoo.org> (2024-05-27)
|
||||
# Requires libpcre2[jit] which is now masked on x32
|
||||
mail-filter/rspamd
|
||||
net-analyzer/ossec-hids
|
||||
|
||||
# James Le Cuirot <chewi@gentoo.org> (2024-02-17)
|
||||
# Requires net-libs/nodejs which is unavailable on amd64/x32.
|
||||
net-misc/sunshine
|
||||
@ -33,6 +38,7 @@ sci-geosciences/viking
|
||||
# Jupyterlab and friends require net-libs/nodejs
|
||||
dev-python/jupyterlab
|
||||
dev-python/jupyterlab-lsp
|
||||
dev-python/jupyterlab-widgets
|
||||
dev-python/jupyter-server-proxy
|
||||
sci-misc/jupyterlab-desktop-bin
|
||||
dev-python/plotly
|
||||
@ -113,8 +119,6 @@ kde-apps/konqueror
|
||||
kde-apps/konsolekalendar
|
||||
kde-apps/kontact
|
||||
kde-apps/korganizer
|
||||
kde-apps/ktp-accounts-kcm
|
||||
kde-apps/ktp-text-ui
|
||||
kde-apps/libksieve
|
||||
kde-apps/mailcommon
|
||||
kde-apps/messagelib
|
||||
@ -122,20 +126,18 @@ kde-apps/mbox-importer
|
||||
kde-apps/parley
|
||||
kde-apps/pim-data-exporter
|
||||
kde-apps/pim-sieve-editor
|
||||
kde-apps/plasma-telepathy-meta:5
|
||||
kde-misc/kio-gdrive
|
||||
kde-misc/tellico
|
||||
kde-misc/zanshin
|
||||
media-gfx/digikam
|
||||
media-gfx/luminance-hdr
|
||||
>=media-gfx/skanpage-24.04.90
|
||||
media-sound/frescobaldi
|
||||
media-sound/teamspeak-client:3
|
||||
media-video/openshot
|
||||
media-video/vidify
|
||||
media-video/vidify-audiosync
|
||||
net-analyzer/nmapsi
|
||||
>=net-im/neochat-24.02.0
|
||||
>=net-im/tokodon-24.02.0
|
||||
net-im/whatsie
|
||||
net-libs/signon-ui
|
||||
sci-geosciences/qmapshack
|
||||
|
||||
@ -1,6 +1,14 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Ben Kohler <bkohler@gentoo.org> (2024-05-27)
|
||||
# Runtime issues (bug #925115) and build issues (bug #931092)
|
||||
dev-libs/libpcre2 jit
|
||||
dev-lang/php jit
|
||||
mail-filter/rspamd jit
|
||||
net-proxy/haproxy pcre-jit
|
||||
www-servers/varnish jit
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-03-24)
|
||||
# Requires unkeyworded dev-qt/qtwebengine
|
||||
net-p2p/ktorrent rss
|
||||
@ -16,7 +24,7 @@ dev-python/iminuit test
|
||||
dev-python/nbdime test
|
||||
dev-python/nbclient test
|
||||
dev-python/nbconvert test
|
||||
dev-python/qiskit-terra visualization
|
||||
dev-python/qiskit visualization
|
||||
sci-mathematics/cadabra jupyter
|
||||
sci-mathematics/yacas jupyter
|
||||
sci-physics/hepmc root
|
||||
@ -85,6 +93,6 @@ www-apps/xpra-html5 minify
|
||||
dev-python/QtPy test
|
||||
|
||||
# Davide Pesavento <pesa@gentoo.org> (2011-11-30)
|
||||
# The QML (V4) and JSC JITs do not work on x32.
|
||||
# The QML (V4) and JSC JITs do not work on x32 (bug #932192).
|
||||
dev-qt/qtdeclarative jit
|
||||
dev-qt/qtscript jit
|
||||
|
||||
@ -5,10 +5,6 @@
|
||||
# Valgrind works on ARMv7
|
||||
-dev-debug/valgrind
|
||||
|
||||
# James Le Cuirot <chewi@gentoo.org> (2015-05-24)
|
||||
# This is built for armv7a so unmask against the wider arm mask.
|
||||
-dev-java/icedtea-bin
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2019-06-22)
|
||||
# This is built for armv7a so unmask here.
|
||||
-dev-java/openjdk-bin:11
|
||||
|
||||
@ -5,10 +5,6 @@
|
||||
# Valgrind works on ARMv7
|
||||
-dev-debug/valgrind
|
||||
|
||||
# James Le Cuirot <chewi@gentoo.org> (2015-05-24)
|
||||
# This is built for armv7a so unmask against the wider arm mask.
|
||||
-dev-java/icedtea-bin
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2019-06-22)
|
||||
# This is built for armv7a so unmask here.
|
||||
-dev-java/openjdk-bin:11
|
||||
|
||||
@ -5,10 +5,6 @@
|
||||
# Valgrind works on ARMv7
|
||||
-dev-debug/valgrind
|
||||
|
||||
# James Le Cuirot <chewi@gentoo.org> (2015-05-24)
|
||||
# This is built for armv7a so unmask against the wider arm mask.
|
||||
-dev-java/icedtea-bin
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2019-06-22)
|
||||
# This is built for armv7a so unmask here.
|
||||
-dev-java/openjdk-bin:11
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
# Copyright 2008-2023 Gentoo Authors
|
||||
# Copyright 2008-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Main ARM profile
|
||||
@ -25,3 +25,7 @@ VIDEO_CARDS="exynos fbdev omap"
|
||||
# Michał Górny <mgorny@gentoo.org> (2017-03-14)
|
||||
# Unhide the ARM-specific USE_EXPANDs.
|
||||
USE_EXPAND_HIDDEN="-CPU_FLAGS_ARM"
|
||||
|
||||
# Hans de Graaff <graaff@gentoo.org> (2024-05-20)
|
||||
# Allow ruby32 stabling: https://bugs.gentoo.org/932285
|
||||
RUBY_TARGETS="ruby31 -ruby32"
|
||||
|
||||
@ -10,10 +10,6 @@
|
||||
# https://valgrind.org/info/platforms.html
|
||||
dev-debug/valgrind
|
||||
|
||||
# James Le Cuirot <chewi@gentoo.org> (2015-05-24)
|
||||
# This is built for armv7a and will not work on earlier generations.
|
||||
dev-java/icedtea-bin
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2019-06-22)
|
||||
# This is built for armv7a and will not work on earlier generations.
|
||||
dev-java/openjdk-bin:11
|
||||
|
||||
@ -1,6 +1,15 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
app-crypt/pinentry qt6
|
||||
app-office/libreoffice qt6
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-06-01)
|
||||
# qtnetworkauth not yet keyworded here
|
||||
dev-python/pyside6 network-auth
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-21)
|
||||
# virt-firmware is keyworded here
|
||||
sys-kernel/installkernel -efistub
|
||||
@ -74,11 +83,7 @@ dev-lang/idris2 test-full
|
||||
dev-python/cloudscraper test
|
||||
dev-python/QtPy test
|
||||
games-util/lgogdownloader gui
|
||||
kde-apps/kde-apps-meta pim
|
||||
kde-apps/kdenetwork-meta bittorrent
|
||||
kde-apps/kleopatra pim
|
||||
kde-apps/umbrello php
|
||||
kde-misc/kio-gdrive share
|
||||
kde-plasma/plasma-nm openconnect
|
||||
net-irc/quassel urlpreview
|
||||
net-misc/fatrat bittorrent
|
||||
net-misc/seafile-client shibboleth
|
||||
@ -114,10 +119,6 @@ app-text/enchant nuspell
|
||||
# Untested useflag on other arches, needs keywording
|
||||
media-video/ffmpeg vmaf
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2022-03-13)
|
||||
# Not yet keyworded. Bug #835037
|
||||
kde-frameworks/kfilemetadata mobi
|
||||
|
||||
# Sam James <sam@gentoo.org> (2022-03-10)
|
||||
# Boost has support for ARM32
|
||||
# https://www.boost.org/doc/libs/1_78_0/libs/context/doc/html/context/architectures.html
|
||||
@ -259,10 +260,6 @@ dev-ruby/capybara test
|
||||
# pre-built, no ARM support
|
||||
net-wireless/gr-osmosdr sdrplay
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2018-06-03)
|
||||
# net-wireless/soapysdr not keyworded
|
||||
net-wireless/gr-osmosdr soapy
|
||||
|
||||
# Markus Meier <maekke@gentoo.org> (2018-05-30)
|
||||
# unkeyworded deps for bug #621434
|
||||
net-analyzer/zmap mongo
|
||||
@ -279,19 +276,11 @@ net-libs/gnutls test-full
|
||||
# Moved from use.mask since they are flags local to one package.
|
||||
media-tv/tvheadend hdhomerun
|
||||
|
||||
# Patrice Clement <monsieurp@gentoo.org> (2017-09-24)
|
||||
# Unmask Raspberry Pi support on arm.
|
||||
media-video/mpv -raspberry-pi
|
||||
|
||||
# James Le Cuirot <chewi@gentoo.org> (2017-09-20)
|
||||
# media-sound/mac's executable segfaults when compressing all but the
|
||||
# smallest wav files.
|
||||
media-sound/xmms2 mac
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2017-08-10)
|
||||
# Requires USE=ipmi which is masked in this profile.
|
||||
sys-power/nut ups_drivers_nut-ipmipsu
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2017-08-08)
|
||||
# Requires USE=opencl that is masked in this profile.
|
||||
net-misc/bfgminer adl lm-sensors
|
||||
@ -368,7 +357,6 @@ net-print/hplip -scanner kde
|
||||
# MMAL is available on the Raspberry Pi (armv6 & armv7 so far)
|
||||
media-video/ffmpeg -mmal
|
||||
media-video/ffmpeg-chromium -mmal
|
||||
media-video/mpv -mmal
|
||||
|
||||
# Alexis Ballier <aballier@gentoo.org> (2015-04-02)
|
||||
# Needs ilmbase (openexr), which does not build and is masked on arm.
|
||||
@ -433,10 +421,6 @@ app-emulation/xen-tools doc
|
||||
# Unkeyworded deps, bug #488724
|
||||
app-office/gnumeric libgda
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-11-28)
|
||||
# Missing keywords, bug #492820
|
||||
net-im/telepathy-connection-managers sipe
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-10-31)
|
||||
# Missing keywords, bug #478254
|
||||
gnome-base/gnome classic extras
|
||||
|
||||
@ -1,6 +1,10 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-29)
|
||||
# media-libs/libplacebo is not stable here
|
||||
media-video/ffmpeg libplacebo
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-21)
|
||||
# Experimental, virt-firmware is keyworded only unstable
|
||||
sys-kernel/installkernel efistub
|
||||
@ -171,10 +175,6 @@ dev-db/mariadb jdbc
|
||||
# RPI support on arm
|
||||
dev-libs/libcec -raspberry-pi
|
||||
|
||||
# Ilya Tumaykin <itumaykin+gentoo@gmail.com> (2016-04-13)
|
||||
# Requires special hardware to test and stabilize properly.
|
||||
media-video/mpv raspberry-pi
|
||||
|
||||
# Brian Evans <grknight@gentoo.org> (2016-01-08)
|
||||
# net-misc/libteam is not yet stable on arm
|
||||
net-misc/networkmanager teamd
|
||||
|
||||
@ -1,12 +1,17 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Unmask the flag which corresponds to ARCH.
|
||||
-arm
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
kf6compat
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2023-02-06)
|
||||
# Successful build of dev-qt/qtwebengine depends on 64-bit host
|
||||
# Bug #893234
|
||||
pdfium
|
||||
webengine
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2022-09-29)
|
||||
|
||||
@ -4,9 +4,9 @@
|
||||
# This file requires eapi 5 or later. New entries go on top.
|
||||
# Please use the same syntax as in use.mask
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-01-27)
|
||||
# Qt6 is not stable here yet
|
||||
qt6
|
||||
# Hans de Graaff <graaff@gentoo.org> (2024-05-20)
|
||||
# Allow ruby32 stabling: https://bugs.gentoo.org/932285
|
||||
ruby_targets_ruby32
|
||||
|
||||
# Sam James <sam@gentoo.org> (2022-01-16)
|
||||
# net-libs/gnome-online-accounts is not marked stable on arm yet
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
# Copyright 2014-2023 Gentoo Authors
|
||||
# Copyright 2014-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Main ARM64 (AArch64/ARMv8) profile; endian independent.
|
||||
|
||||
@ -1,6 +1,23 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-23)
|
||||
# Pulls in kde-apps/kgpg is keyworded here
|
||||
>=kde-apps/kdeutils-meta-24.05.1 -gpg
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
app-crypt/pinentry qt6
|
||||
app-office/libreoffice qt6
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-05-19)
|
||||
# jit is supported here
|
||||
>=dev-qt/qtdeclarative-6 -jit
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2024-05-09)
|
||||
# Unmask for keywording bug #931634
|
||||
x11-libs/libdrm -video_cards_vmware
|
||||
|
||||
# Paul Zander <negril.nx+gentoo@gmail.com> (2024-04-12)
|
||||
# Supports 64-bit NEON
|
||||
media-libs/opencv -cpu_flags_arm_neon
|
||||
@ -13,11 +30,6 @@ media-libs/openpgl -cpu_flags_arm_neon
|
||||
# virt-firmware is keyworded here
|
||||
sys-kernel/installkernel -efistub
|
||||
|
||||
# Mart Raudsepp <leio@gentoo.org> (2024-03-03)
|
||||
# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff)
|
||||
# are only available for amd64, arm64 and riscv
|
||||
>=gui-libs/wlroots-0.17.0 -drm -liftoff
|
||||
|
||||
# Joonas Niilola <juippis@gentoo.org> (2024-02-16)
|
||||
# Test dependencies not keyworded on this arch.
|
||||
www-servers/nginx test
|
||||
@ -470,10 +482,6 @@ app-text/evince dvi nautilus postscript xps
|
||||
# Unkeyworded deps, bug #488724
|
||||
app-office/gnumeric libgda
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-11-28)
|
||||
# Missing keywords, bug #492820
|
||||
net-im/telepathy-connection-managers sipe
|
||||
|
||||
# Sergey Popov <pinkbyte@gentoo.org> (2013-09-06)
|
||||
# sci-libs/hdf does not build properly on arm
|
||||
dev-perl/PDL hdf
|
||||
|
||||
@ -1,15 +1,18 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Eray Aslan <eras@gentoo.org> (2024-06-17)
|
||||
# mongodb needed for tests which is not stable keyworded for arm64
|
||||
dev-libs/mongo-c-driver test
|
||||
|
||||
# Sam Jamrs <sam@gentoo.org> (2024-06-07)
|
||||
# dev-libs/capstone hasn't been stabilized yet
|
||||
app-emulation/qemu capstone
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-21)
|
||||
# Experimental, virt-firmware is keyworded only unstable
|
||||
sys-kernel/installkernel efistub
|
||||
|
||||
# Mart Raudsepp <leio@gentoo.org> (2024-03-03)
|
||||
# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff)
|
||||
# are not stable yet on arm64
|
||||
>=gui-libs/wlroots-0.17.0 drm liftoff
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-01-27)
|
||||
# dev-python/PyQt6 and dev-python/pyside6 are not stable here yet
|
||||
dev-python/QtPy pyqt6 pyside6
|
||||
|
||||
@ -1,9 +1,13 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Unmask the flag which corresponds to ARCH.
|
||||
-arm64
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
kf6compat
|
||||
|
||||
# Paul Zander <negril.nx+gentoo@gmail.com> (2024-03-28)
|
||||
# dev-libs/optix works on arm64
|
||||
-optix
|
||||
@ -121,30 +125,26 @@ anthy
|
||||
snapcast
|
||||
|
||||
# Unmask ARM-only video-cards
|
||||
-video_cards_amdgpu
|
||||
-video_cards_d3d12
|
||||
-video_cards_exynos
|
||||
-video_cards_freedreno
|
||||
-video_cards_lima
|
||||
-video_cards_nouveau
|
||||
-video_cards_panfrost
|
||||
-video_cards_radeon
|
||||
-video_cards_radeonsi
|
||||
-video_cards_tegra
|
||||
-video_cards_v3d
|
||||
-video_cards_vc4
|
||||
-video_cards_amdgpu
|
||||
-video_cards_radeon
|
||||
-video_cards_radeonsi
|
||||
|
||||
# James Le Cuirot <chewi@gentoo.org>
|
||||
# Unmask as Vivante is available for arm.
|
||||
-video_cards_vivante
|
||||
-video_cards_vmware
|
||||
|
||||
# Donnie Berkholz <dberkholz@gentoo.org> (2006-02-05)
|
||||
# Modular X: mask for architectures on which they aren't available
|
||||
video_cards_mga
|
||||
video_cards_r128
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org>
|
||||
# Mask more VIDEO_CARDs added with mesa-8.0
|
||||
video_cards_r100
|
||||
video_cards_r128
|
||||
video_cards_r200
|
||||
video_cards_r300
|
||||
video_cards_r600
|
||||
|
||||
@ -4,6 +4,14 @@
|
||||
# This file requires eapi 5 or later. New entries go on top.
|
||||
# Please use the same syntax as in use.mask
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2024-05-10)
|
||||
# x11-drivers/xf86-video-vmware is not stable yet
|
||||
video_cards_vmware
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2024-05-10)
|
||||
# dev-util/directx-headers is not stable yet
|
||||
video_cards_d3d12
|
||||
|
||||
# Mart Raudsepp <leio@gentoo.org> (2023-10-03)
|
||||
# dev-util/sysprof-capture and dev-util/sysprof are not stable yet
|
||||
sysprof
|
||||
|
||||
@ -1,9 +1,23 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-23)
|
||||
# Pulls in kde-apps/kgpg which requires kde-apps/akonadi, which is as
|
||||
# part of the KDE PIM stack (big, requiring QtWebengine) only keyworded
|
||||
# on amd64 and arm64.
|
||||
>=kde-apps/kdeutils-meta-24.05.1 gpg
|
||||
|
||||
# Jared Allard <jared@rgst.io> (2024-06-21)
|
||||
# uasm and jwasm include amd64-specific ASM
|
||||
app-arch/7zip uasm jwasm
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-04-25)
|
||||
# ROCm and Level-Zero are amd64-only at the moment
|
||||
sys-apps/hwloc rocm l0
|
||||
|
||||
# Paul Zander <negril.nx+gentoo@gmail.com> (2024-04-20)
|
||||
# only keyworded for amd64 currently
|
||||
media-gfx/blender gnome
|
||||
media-gfx/blender gnome oneapi renderdoc vulkan
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-04-16)
|
||||
# dev-qt/qtlanguageserver:6 currently has very few keywords
|
||||
@ -55,11 +69,6 @@ sys-kernel/gentoo-kernel-bin generic-uki
|
||||
# Needs dev-qt/qtwebengine:6 which has very few keywords.
|
||||
dev-python/PyQt6 pdfium
|
||||
|
||||
# Leonardo Hernández Hernández <leohdz172@proton.me> (2023-11-25)
|
||||
# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff)
|
||||
# are only available for amd64, arm64 and riscv
|
||||
>=gui-libs/wlroots-0.17.0 drm liftoff
|
||||
|
||||
# Jimi Huotari <chiitoo@gentoo.org> (2023-11-22)
|
||||
# media-libs/libvpl is only keyworded for amd64 at this time.
|
||||
media-video/obs-studio qsv
|
||||
@ -103,6 +112,7 @@ www-servers/apache apache2_modules_tls
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-04-22)
|
||||
# snap only works on amd64
|
||||
gnome-extra/gnome-software snap
|
||||
kde-plasma/discover snap
|
||||
|
||||
# Sam James <sam@gentoo.org> (2023-04-03)
|
||||
@ -110,10 +120,6 @@ kde-plasma/discover snap
|
||||
# See bug #894078.
|
||||
dev-python/tables cpudetection
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2023-03-09)
|
||||
# media-libs/libplacebo is not keyworded anywhere except amd64/ppc64/x86 yet
|
||||
media-video/ffmpeg libplacebo
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2023-01-24)
|
||||
# libomptarget is only supported on 64-bit architectures.
|
||||
>=sys-libs/libomp-16.0.0_pre20230124 offload
|
||||
@ -131,7 +137,6 @@ net-misc/curl rustls curl_ssl_rustls
|
||||
# Quick Sync Video (through intel-mediasdk or oneVPL) is
|
||||
# only keyworded on amd64
|
||||
media-video/ffmpeg qsv
|
||||
media-libs/gst-plugins-bad qsv
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2022-12-01)
|
||||
# Only supported on ppc64le.
|
||||
@ -231,6 +236,7 @@ sys-libs/compiler-rt-sanitizers asan dfsan lsan msan hwasan tsan
|
||||
sys-libs/compiler-rt-sanitizers ubsan safestack cfi scudo
|
||||
sys-libs/compiler-rt-sanitizers shadowcallstack gwp-asan
|
||||
sys-libs/compiler-rt-sanitizers libfuzzer memprof orc profile xray
|
||||
sys-libs/compiler-rt-sanitizers ctx-profile
|
||||
|
||||
# Sam James <sam@gentoo.org> (2020-10-24)
|
||||
# asm redc is only available on amd64,
|
||||
@ -304,10 +310,6 @@ dev-java/openjdk:11 javafx
|
||||
# dev-lang/spidermonkey:60[jit] fails to build on most platforms
|
||||
>=dev-lang/spidermonkey-60 jit
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2019-05-09)
|
||||
# media-libs/libplacebo is not keyworded anywhere except amd64/ppc64/x86 yet
|
||||
media-video/vlc libplacebo
|
||||
|
||||
# Denis Lisov <dennis.lissov@gmail.com> (2019-05-09)
|
||||
# Overlay can only be built on amd64 and x86
|
||||
x11-apps/igt-gpu-tools overlay
|
||||
@ -384,19 +386,12 @@ dev-db/mariadb jdbc
|
||||
# This flag only has meaning on amd64
|
||||
sys-boot/grub:2 grub_platforms_xen-32
|
||||
|
||||
# Ian Delaney <idella4@gentoo.org> (2016-04-06)
|
||||
# on behalf of Ilya Tumaykin <itumaykin+gentoo@gmail.com>
|
||||
# Raspberry Pi support is only available on arm.
|
||||
# Mask raspberry-pi USE globally, unmask on arm.
|
||||
media-video/mpv raspberry-pi
|
||||
|
||||
# Alexis Ballier <aballier@gentoo.org> (2015-11-14)
|
||||
# MMAL is only available on the Raspberry Pi:
|
||||
# Mask it globally, unmask it on arm.
|
||||
media-video/motion mmal
|
||||
media-video/ffmpeg mmal
|
||||
media-video/ffmpeg-chromium mmal
|
||||
media-video/mpv mmal
|
||||
|
||||
# Brian Evans <grknight@gentoo.org> (2015-09-14)
|
||||
# Mask new USE flags for mariadb which all arches do not yet have dependencies
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
ARCH="hppa"
|
||||
@ -22,3 +22,7 @@ CHOST_hppa="${CHOST}"
|
||||
# Donnie Berkholz <dberkholz@gentoo.org> (2006-08-18)
|
||||
# Defaults for video drivers
|
||||
VIDEO_CARDS="fbdev"
|
||||
|
||||
# Hans de Graaff <graaff@gentoo.org> (2024-05-20)
|
||||
# Allow ruby32 stabling: https://bugs.gentoo.org/932285
|
||||
RUBY_TARGETS="ruby31 -ruby32"
|
||||
|
||||
@ -4,6 +4,24 @@
|
||||
# NOTE: When masking a USE flag due to missing keywords, please file a keyword
|
||||
# request bug for the hppa arch.
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-19)
|
||||
# The systemd implementation of installkernel doesn't currently support
|
||||
# updating the 'initramfs.img' and 'vmlinuz' symlinks that palo needs,
|
||||
# and palo is the only bootloader for HPPA.
|
||||
sys-kernel/installkernel systemd
|
||||
|
||||
# Holger Hoffstätte <holger@applied-asynchrony.com> (2024-05-19)
|
||||
# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559
|
||||
media-gfx/graphicsmagick jpeg2k
|
||||
|
||||
# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-13)
|
||||
# Requires dev-util/shelltestrunner
|
||||
app-arch/mt-st test
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-05-08)
|
||||
# Requires sys-devel/{clang,llvm}:16.
|
||||
dev-lang/python jit
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-01-23)
|
||||
# Needs dev-qt/qtquick3d:6 which itself needs media-libs/assimp that
|
||||
# is not keyworded here and currently fails tests (bug #919896).
|
||||
@ -58,10 +76,6 @@ dev-build/cmake gui
|
||||
# x11-libs/gtksourceview:4 not keyworded here
|
||||
media-gfx/inkscape sourceview
|
||||
|
||||
# Rich Freeman <rich0@gentoo.org> (2023-09-13)
|
||||
# Tests require shellcheck which is not currently available on hppa
|
||||
sys-process/systemd-cron test
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2023-05-30)
|
||||
# sys-apps/dbus-broker is not keyworded
|
||||
app-accessibility/at-spi2-core dbus-broker
|
||||
@ -242,7 +256,7 @@ dev-libs/efl avif lua_single_target_luajit physics
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2020-08-11)
|
||||
# No drivers on this architecture support Vulkan
|
||||
media-libs/mesa vulkan vulkan-overlay zink
|
||||
media-libs/mesa video_cards_zink vulkan vulkan-overlay zink
|
||||
|
||||
# Robin H. Johnson <robbat2@gentoo.org> (2020-07-02)
|
||||
# Mask io-uring & zbc pending keywording
|
||||
|
||||
@ -4,6 +4,10 @@
|
||||
# This file requires eapi 5 or later. New entries go on top.
|
||||
# Please use the same syntax as in use.mask
|
||||
|
||||
# Hans de Graaff <graaff@gentoo.org> (2024-05-20)
|
||||
# Allow ruby32 stabling: https://bugs.gentoo.org/932285
|
||||
ruby_targets_ruby32
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-01-27)
|
||||
# Qt6 is not stable here yet
|
||||
qt6
|
||||
|
||||
@ -1,6 +1,26 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-29)
|
||||
# media-libs/libplacebo is not keyworded
|
||||
media-video/ffmpeg libplacebo
|
||||
|
||||
# Thomas Bettler <thomas.bettler@gmail.com> (2024-06-10)
|
||||
# requires dev-libs/apache-arrow which is net yet keyworded
|
||||
sci-libs/gdal parquet
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-05-19)
|
||||
# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559
|
||||
media-gfx/graphicsmagick jpeg2k
|
||||
|
||||
# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-13)
|
||||
# Requires dev-util/shelltestrunner
|
||||
app-arch/mt-st test
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-05-08)
|
||||
# Requires sys-devel/{clang,llvm}:16.
|
||||
dev-lang/python jit
|
||||
|
||||
# Robin H. Johnson <robbat2@gentoo.org) (2024-03-13)
|
||||
# sys-cluster/corosync not yet keyworded, niche use case for mdadm
|
||||
sys-fs/mdadm corosync
|
||||
@ -62,10 +82,6 @@ app-text/doxygen gui
|
||||
# Qt 6 not keyworded here.
|
||||
dev-build/cmake gui
|
||||
|
||||
# Rich Freeman <rich0@gentoo.org> (2023-09-13)
|
||||
# Tests require shellcheck which is not currently available
|
||||
sys-process/systemd-cron test
|
||||
|
||||
# Jon Janzen <jon@jonjanzen.com> (2023-09-11)
|
||||
# librttopo has not been tested on this arch
|
||||
dev-db/spatialite rttopo
|
||||
@ -223,7 +239,7 @@ net-analyzer/wireshark gui ilbc
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2020-08-11)
|
||||
# No drivers on this architecture support Vulkan
|
||||
media-libs/mesa vulkan vulkan-overlay zink
|
||||
media-libs/mesa video_cards_zink vulkan vulkan-overlay zink
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2020-06-14)
|
||||
# Requires dev-python/networkx.
|
||||
@ -487,10 +503,6 @@ gnome-base/gnome classic extras
|
||||
# Missing keywords, bug #493156
|
||||
media-libs/libgphoto2 serial
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-11-28)
|
||||
# Missing keywords, bug #492820
|
||||
net-im/telepathy-connection-managers sipe
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-07-20)
|
||||
# Keywords pending, bug #476710
|
||||
>=gnome-base/gnome-extra-apps-3.8 games
|
||||
|
||||
@ -1,11 +1,6 @@
|
||||
# Copyright 2022-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (@024-03-07)
|
||||
# This version fails to build here due to the used crates, and
|
||||
# will wait for next bump rather than try to fix it (bug #926407)
|
||||
~dev-util/maturin-1.5.0
|
||||
|
||||
# WANG Xuerui <xen0n@gentoo.org> (2023-09-10)
|
||||
# Has correctness issues on loong (failing test_encode_long_neg_conversion),
|
||||
# pending debug.
|
||||
|
||||
@ -1,11 +1,24 @@
|
||||
# Copyright 2022-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# WANG Xuerui <xen0n@gentoo.org> (2024-04-04)
|
||||
# dev-qt/qtwebengine is not available on loong (no upstream Chromium support,
|
||||
# patchset not integrated yet)
|
||||
>=kde-apps/kdecore-meta-24 handbook
|
||||
kde-plasma/plasma-meta:6 handbook
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-15)
|
||||
# Requires unkeyworded dev-qt/qtwebengine (and revdeps)
|
||||
kde-plasma/plasma-nm openconnect
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
app-crypt/pinentry qt6
|
||||
app-office/libreoffice qt6
|
||||
|
||||
# WANG Xuerui <xen0n@gentoo.org> (2024-06-03)
|
||||
# Requires arch-specific code in python (relocs handling), in addition to
|
||||
# sys-devel/{clang,llvm}.
|
||||
dev-lang/python jit
|
||||
|
||||
# WANG Xuerui <xen0n@gentoo.org> (2024-05-16)
|
||||
# dev-ruby/asciidoctor has some really heavy deps, and is not keyworded on
|
||||
# loong yet.
|
||||
net-misc/chrony html
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-03-27)
|
||||
# No rust-bin available for profiler
|
||||
@ -81,6 +94,7 @@ dev-python/requests-cache test
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-08-30)
|
||||
# Avoid having to keyword more Qt deps
|
||||
dev-python/pyside2 3d datavis location scxml
|
||||
dev-python/pyside6 3d location scxml
|
||||
|
||||
# WANG Xuerui <xen0n@gentoo.org> (2023-07-26)
|
||||
# no llvm:15 or lld:16 on loong
|
||||
@ -143,11 +157,6 @@ sys-kernel/installkernel -systemd-boot -ukify -uki
|
||||
# dev-python/pyopengl fails tests
|
||||
dev-python/sympy opengl
|
||||
|
||||
# WANG Xuerui <xen0n@gentoo.org> (2023-04-16)
|
||||
# dev-python/aesara doesn't work on loong yet (due to hardcoding -m64 in its
|
||||
# cc invocations)
|
||||
dev-python/sympy aesara
|
||||
|
||||
# WANG Xuerui <xen0n@gentoo.org> (2022-12-06)
|
||||
# dev-cpp/glog fails tests, needs checking
|
||||
media-libs/opencv glog contribsfm
|
||||
|
||||
@ -1,6 +1,10 @@
|
||||
# Copyright 2022-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
kf6compat
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-02-05)
|
||||
# LLVM slots without keywords.
|
||||
llvm_slot_15
|
||||
@ -39,6 +43,7 @@ nas
|
||||
|
||||
# WANG Xuerui <xen0n@gentoo.org> (2022-11-01)
|
||||
# qtwebengine isn't available on loong yet
|
||||
pdfium
|
||||
webengine
|
||||
|
||||
# Unmask the flag which corresponds to ARCH.
|
||||
|
||||
6
sdk_container/src/third_party/portage-stable/profiles/arch/m68k/package.mask
vendored
Normal file
6
sdk_container/src/third_party/portage-stable/profiles/arch/m68k/package.mask
vendored
Normal file
@ -0,0 +1,6 @@
|
||||
# Copyright 2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Andreas K. Hüttel <dilfridge@gentoo.org>
|
||||
# Requires 32bit alignment, so we mask it for the moment
|
||||
dev-lang/python:3.13
|
||||
@ -1,6 +1,10 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-05-08)
|
||||
# Requires sys-devel/{clang,llvm}:16.
|
||||
dev-lang/python jit
|
||||
|
||||
# James Le Cuirot (2023-12-12)
|
||||
# USE=bpf depends on sys-devel/clang which is not keyworded on m68k
|
||||
media-libs/libv4l bpf
|
||||
|
||||
@ -157,3 +157,7 @@ slang
|
||||
tcl
|
||||
tk
|
||||
xemacs
|
||||
|
||||
# Andreas K. Hüttel <dilfridge@gentoo.org>
|
||||
# Requires 32bit alignment, so we mask it for the moment
|
||||
python_targets_python3_13
|
||||
|
||||
6
sdk_container/src/third_party/portage-stable/profiles/arch/mips/mips64/package.use.mask
vendored
Normal file
6
sdk_container/src/third_party/portage-stable/profiles/arch/mips/mips64/package.use.mask
vendored
Normal file
@ -0,0 +1,6 @@
|
||||
# Copyright 2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2024-05-01)
|
||||
# Sanitizers supported on 64-bit mips only, #779742
|
||||
sys-libs/compiler-rt-sanitizers -dfsan -lsan -msan -tsan -cfi
|
||||
@ -1,6 +1,32 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Arthur Zamarin <arthurzam@gentoo.org> (2024-07-01)
|
||||
# simplify the dep tree
|
||||
dev-python/click doc
|
||||
dev-python/cython doc
|
||||
dev-python/flake8 doc
|
||||
dev-python/flask doc
|
||||
dev-python/flit doc
|
||||
dev-python/greenlet doc
|
||||
dev-python/outcome doc
|
||||
dev-python/pytest-cov doc
|
||||
dev-python/pytest-trio doc
|
||||
dev-python/stevedore doc
|
||||
dev-python/sphinx-autodoc-typehints test
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-29)
|
||||
# media-libs/libplacebo is not keyworded
|
||||
media-video/ffmpeg libplacebo
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-05-08)
|
||||
# Requires sys-devel/{clang,llvm}:16.
|
||||
dev-lang/python jit
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2024-05-01)
|
||||
# Sanitizers supported on both 32-bit and 64-bit mips, #779742
|
||||
sys-libs/compiler-rt-sanitizers -asan -profile -ubsan -safestack -scudo -xray
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2024-03-21)
|
||||
# Test suite is very fragile and doesn't even run on amd64.
|
||||
# No real point in running it here right now, bug #804115.
|
||||
@ -99,10 +125,6 @@ net-dns/ddclient test
|
||||
dev-lang/gnat-gpl -fixed-point
|
||||
sys-devel/gcc -fixed-point
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2022-09-14)
|
||||
# Not broken, but better wait on profiles: bug #515694
|
||||
dev-lang/rust system-llvm
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2022-04-18)
|
||||
# app-text/nuspell is not keyworded
|
||||
app-text/enchant nuspell
|
||||
@ -139,14 +161,6 @@ dev-libs/libgudev test
|
||||
# dev-python/django is not keyworded here
|
||||
dev-python/diskcache test
|
||||
|
||||
# Joshua Kinard <kumba@gentoo.org> (2021-05-20)
|
||||
# mask USE 'test' on MIPS for setuptools and jaraco-path due to
|
||||
# the very deep dependency chain that is enabled. Will unmask
|
||||
# on a future date.
|
||||
# Bug #774216
|
||||
dev-python/jaraco-path test
|
||||
dev-python/setuptools test
|
||||
|
||||
# Sam James <sam@gentoo.org> (2021-02-06)
|
||||
# media-sound/sndio is not yet keyworded here
|
||||
# bug #769098, bug #769122
|
||||
@ -265,9 +279,6 @@ media-video/mplayer ladspa
|
||||
# app-xemacs/ruby-modes is not keyworded on this arch
|
||||
dev-lang/ruby xemacs
|
||||
|
||||
# deps missing keywords
|
||||
games-strategy/freeciv auth
|
||||
|
||||
# Mart Raudsepp <leio@gentoo.org> (2010-09-27)
|
||||
# Extra functionality that has external unkeyworded dependencies
|
||||
# and is not tested yet
|
||||
|
||||
@ -240,11 +240,6 @@ rpm
|
||||
# We don't have net-libs/libsmi keyworded
|
||||
smi
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2010-12-13)
|
||||
# We don't have sys-devel/llvm
|
||||
llvm
|
||||
llvm-libunwind
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2011-06-14)
|
||||
# pdfannotextractor needs java
|
||||
pdfannotextractor
|
||||
|
||||
@ -1,6 +1,14 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Thomas Bettler <thomas.bettler@gmail.com> (2024-06-10)
|
||||
# requires dev-libs/apache-arrow which is net yet keyworded
|
||||
sci-libs/gdal parquet
|
||||
|
||||
# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-13)
|
||||
# Requires dev-util/shelltestrunner
|
||||
app-arch/mt-st test
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-03-31)
|
||||
# MPV currently[1] has no plans to support >=lua5-3 making luajit
|
||||
# the only choice for maintained lua. Apply mask/force to override
|
||||
@ -13,6 +21,7 @@ media-video/mpv -lua_single_target_lua5-1 lua_single_target_luajit
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-03-24)
|
||||
# Requires unkeyworded dev-qt/qtwebengine (and revdeps)
|
||||
kde-apps/kleopatra pim
|
||||
kde-plasma/plasma-nm openconnect
|
||||
net-irc/quassel urlpreview
|
||||
net-p2p/ktorrent rss
|
||||
|
||||
@ -72,6 +81,7 @@ dev-db/spatialite rttopo
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-08-30)
|
||||
# Avoid keywordming more Qt stuff
|
||||
dev-python/pyside2 3d datavis scxml
|
||||
dev-python/pyside6 3d scxml
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-03-07)
|
||||
# nbval/nbclassic docs require pandoc which is not keyworded here yet
|
||||
@ -178,10 +188,6 @@ www-client/chromium widevine
|
||||
# requires media-libs/sdl2-image, which is not yet keyworded
|
||||
app-emulation/qemu sdl-image
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-25)
|
||||
# requires fwupd, which is not yet keyworded
|
||||
kde-plasma/discover firmware
|
||||
|
||||
# Rick Farina <zerochaos@gentoo.org> (2020-01-03)
|
||||
# ubertooth needs net-libs/libbtbb and net-wireless/ubertooth which aren't keyworded
|
||||
net-wireless/kismet ubertooth
|
||||
@ -266,10 +272,6 @@ app-i18n/fcitx-libpinyin dictionary-manager
|
||||
# Requires java
|
||||
app-forensics/sleuthkit java
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2017-08-10)
|
||||
# Requires USE=ipmi which is masked in this profile.
|
||||
sys-power/nut ups_drivers_nut-ipmipsu
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2017-08-08)
|
||||
# Requires USE=opencl that is masked in this profile.
|
||||
net-misc/bfgminer adl lm-sensors
|
||||
@ -347,10 +349,6 @@ media-libs/opencv vtk
|
||||
# Missing keywords, bug #495250
|
||||
>=gnome-base/gnome-extra-apps-3.10 tracker
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-11-28)
|
||||
# Missing keywords, bug #492820
|
||||
net-im/telepathy-connection-managers sipe
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-10-31)
|
||||
# Missing keywords, bug #478254
|
||||
gnome-base/gnome classic extras
|
||||
|
||||
@ -17,6 +17,11 @@
|
||||
|
||||
#--- END OF EXAMPLES ---
|
||||
|
||||
# Joonas Niilola <juippis@gentoo.org> (2024-05-28)
|
||||
# Depchain-destabilization on ppc (libsecret[test-rust] -> gjs -> spidermonkey)
|
||||
app-crypt/libsecret test-rust
|
||||
dev-util/glade gjs
|
||||
|
||||
# Mart Raudsepp <leio@gentoo.org> (2023-12-25)
|
||||
# Libei not stable here yet
|
||||
x11-base/xwayland libei
|
||||
@ -40,7 +45,7 @@ media-sound/jack2 ieee1394
|
||||
|
||||
# Sam James <sam@gentoo.org> (2020-07-30)
|
||||
# vulkan-loader and glslang are not yet stable on ppc
|
||||
media-libs/mesa vulkan vulkan-overlay zink
|
||||
media-libs/mesa video_cards_zink vulkan vulkan-overlay zink
|
||||
|
||||
# Sergei Trofimovich <slyfox@gentoo.org> (2019-12-12)
|
||||
# Needs stable net-libs/webkit-gtk, bug #684702
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# All extra USE/etc should be specified in sub-profiles.
|
||||
|
||||
@ -1,6 +1,10 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-05-19)
|
||||
# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559
|
||||
media-gfx/graphicsmagick jpeg2k
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-03-23)
|
||||
# sys-libs/libomp does not support ppc32 (bug #907213).
|
||||
sys-devel/clang-runtime openmp
|
||||
@ -9,10 +13,7 @@ sys-devel/clang-runtime openmp
|
||||
# Fails tests, potential false negatives #911402
|
||||
app-antivirus/clamav system-mspack
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-01-17)
|
||||
# The generated code is too large and it takes ages to build, bug #922249.
|
||||
dev-python/mypy native-extensions
|
||||
|
||||
# Marek Szuba <marecki@gentoo.org> (2024-04-24)
|
||||
# Sam James <sam@gentoo.org> (2024-01-05)
|
||||
# sys-apps/keyutils not stable here, because of test failures. bug #636252
|
||||
app-benchmarks/stress-ng keyutils
|
||||
@ -20,7 +21,7 @@ app-crypt/mit-krb5 keyutils
|
||||
app-emulation/qemu keyutils
|
||||
net-fs/cifs-utils ads creds pam
|
||||
net-fs/samba ads
|
||||
sys-auth/sssd keyutils
|
||||
>=sys-libs/libblockdev-3.0.0 cryptsetup
|
||||
sys-libs/libnvme keyutils
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2023-10-15)
|
||||
|
||||
@ -1,6 +1,10 @@
|
||||
# Copyright 2014-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-06-09)
|
||||
# Qt6 is not stable here yet
|
||||
qt6
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-03-07)
|
||||
# dev-lang/php:8.2 is not marked stable here yet (bug #920701)
|
||||
php_targets_php8-2
|
||||
|
||||
@ -1,14 +1,22 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# WARNING: UnmatchedProfilePackageUnmask has a bug with false positives here
|
||||
# https://github.com/pkgcore/pkgcheck/issues/685
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2024-06-10)
|
||||
# Unmask for ppc64le, #892183
|
||||
-dev-python/sympy
|
||||
-dev-python/symengine
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-04-24)
|
||||
# Unmask ppc64le binpkg.
|
||||
-dev-python/pypy-exe-bin
|
||||
|
||||
# Rahil Bhimjiani <me@rahil.rocks> (2024-03-20)
|
||||
# https://bugs.gentoo.org/925111
|
||||
-app-containers/podman
|
||||
|
||||
# Jimi Huotari <chiitoo@gentoo.org> (2023-01-11)
|
||||
# Requires media-libs/libva since 29.0.0, which is unmasked here.
|
||||
->=media-video/obs-studio-29.0.0
|
||||
|
||||
# Sam James <sam@gentoo.org> (2022-01-18)
|
||||
# No bootstrap binary available on big endian PPC64 right now, but there is
|
||||
# one for ppc64le.
|
||||
@ -64,16 +72,6 @@
|
||||
-sys-kernel/vanilla-kernel
|
||||
-virtual/dist-kernel
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-25)
|
||||
# libva unmasked on little-endian profile
|
||||
-net-im/telegram-desktop
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-21)
|
||||
# works fine on little-endian
|
||||
-media-libs/libva
|
||||
-media-video/libva-utils
|
||||
-media-plugins/gst-plugins-vaapi
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2019-08-14)
|
||||
# works fine on little-endian
|
||||
-x11-drivers/xf86-video-amdgpu
|
||||
|
||||
@ -5,10 +5,6 @@
|
||||
# Needs USE=video_cards_amdgpu, which IS available on ppc64le.
|
||||
>=sys-apps/fwupd-1.9.10 -amdgpu
|
||||
|
||||
# Craig Andrews <candrews@gentoo.org> (2023-03-09)
|
||||
# media-libs/libplacebo is keyworded here
|
||||
media-video/ffmpeg -libplacebo
|
||||
|
||||
# Joonas Niilola <juippis@gentoo.org> (2022-11-10)
|
||||
# Doesn't work on ppc64, #871921
|
||||
sci-mathematics/gmp-ecm custom-tune
|
||||
|
||||
@ -1,10 +1,20 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2024-06-10)
|
||||
# Requires ieee-long-double, i.e. ppc64le with 23.0
|
||||
# profiles and up, #892183
|
||||
dev-python/sympy
|
||||
dev-python/symengine
|
||||
|
||||
# Rahil Bhimjiani <me@rahil.rocks> (2024-03-20)
|
||||
# https://bugs.gentoo.org/925111
|
||||
app-containers/podman
|
||||
|
||||
# Jimi Huotari <chiitoo@gentoo.org> (2023-01-11)
|
||||
# Requires media-libs/libva since 29.0.0, which is masked here.
|
||||
>=media-video/obs-studio-29.0.0
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-25)
|
||||
# Not all dependencies keyworded
|
||||
net-im/telegram-desktop
|
||||
|
||||
@ -1,6 +1,11 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Joonas Niilola <juippis@gentoo.org> (2023-08-24)
|
||||
# media-video/libva-utils is masked on ppc64, so hwaccel on Firefox
|
||||
# wouldn't work.
|
||||
www-client/firefox hwaccel
|
||||
|
||||
# Georgy Yakovlev (2022-02-16)
|
||||
# dev-python/networkx is keyworded here
|
||||
app-portage/nattka -depgraph-order
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# All extra USE/etc should be specified in sub-profiles.
|
||||
|
||||
@ -1,10 +1,6 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Jimi Huotari <chiitoo@gentoo.org> (2023-01-11)
|
||||
# Requires media-libs/libva since 29.0.0.
|
||||
>=media-video/obs-studio-29.0.0
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2022-08-25)
|
||||
# Only ppc64le binpkg is provided.
|
||||
dev-python/pypy-exe-bin
|
||||
@ -61,12 +57,6 @@ sys-kernel/gentoo-kernel-bin
|
||||
sys-kernel/vanilla-kernel
|
||||
virtual/dist-kernel
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-21)
|
||||
# buggy on big-endian
|
||||
media-libs/libva
|
||||
media-video/libva-utils
|
||||
media-plugins/gst-plugins-vaapi
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2019-08-14)
|
||||
# buggy on big-endian
|
||||
x11-drivers/xf86-video-amdgpu
|
||||
|
||||
@ -1,6 +1,15 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
app-crypt/pinentry qt6
|
||||
app-office/libreoffice qt6
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-05-19)
|
||||
# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559
|
||||
media-gfx/graphicsmagick jpeg2k
|
||||
|
||||
# José de Paula R. N. Assis <espinafre@gmail.com> (2024-03-25)
|
||||
# No PyQt6 (which is needed by USE=qt6 for qscintilla-python) on ppc64.
|
||||
>=dev-python/qscintilla-python-2.14.1-r1 qt6
|
||||
@ -21,11 +30,6 @@ media-libs/libplacebo -shaderc
|
||||
# Qt 6 not keyworded here.
|
||||
dev-build/cmake gui
|
||||
|
||||
# Joonas Niilola <juippis@gentoo.org> (2023-08-24)
|
||||
# media-video/libva-utils is masked on ppc64, so hwaccel on Firefox
|
||||
# wouldn't work.
|
||||
www-client/firefox hwaccel
|
||||
|
||||
# Alexey Sokolov <alexey+gentoo@asokolov.org> (2023-08-14)
|
||||
# OpenMW is only playtested with LuaJIT, and in fact unit tests fail with Lua-5.
|
||||
# Therefore apply mask/force to override the profile's defaults, and invert on
|
||||
@ -55,10 +59,6 @@ sci-libs/symengine tcmalloc
|
||||
# https://github.com/rustsec/rustsec/issues/707
|
||||
dev-util/cargo-audit fix
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2022-07-17)
|
||||
# dev-python/pyside2 is not keyworded
|
||||
www-client/falkon python
|
||||
|
||||
# Jimi Huotari <chiitoo@gentoo.org> (2022-05-08)
|
||||
# Not keyworded here yet.
|
||||
lxqt-base/lxqt-meta desktop-portal
|
||||
@ -136,10 +136,6 @@ x11-themes/arc-theme cinnamon
|
||||
# Bug #728558
|
||||
media-video/ffmpeg -rav1e
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2020-07-02)
|
||||
# media-libs/libplacebo is keyworded
|
||||
media-video/vlc -libplacebo
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-06-07)
|
||||
# works on ppc64
|
||||
app-emulation/qemu -spice -usbredir
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# When you add an entry to the top of this file, add your name, the date, and
|
||||
@ -17,6 +17,14 @@
|
||||
|
||||
#--- END OF EXAMPLES ---
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-04-30)
|
||||
# sys-block/nbdkit is not yet marked stable here
|
||||
app-emulation/libvirt nbd
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-04-24)
|
||||
# sys-apps/flashrom is not marked stable on ppc64 yet
|
||||
sys-apps/fwupd flashrom
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-02-07)
|
||||
# grpc not stable here
|
||||
app-admin/syslog-ng grpc
|
||||
|
||||
@ -1,8 +1,12 @@
|
||||
# Copyright 2008-2023 Gentoo Authors
|
||||
# Copyright 2008-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
### THIS FILE IS ONLY FOR PACKAGES MASKED ON BOTH 64-BIT AND 32-BIT USERLAND!!!
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
kf6compat
|
||||
|
||||
# Paul Zander <negril.nx+gentoo@gmail.com> (2024-03-29)
|
||||
# not available here (see openexr, opencolorio, opencv)
|
||||
openvdb
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# PPC Specific use flags
|
||||
@ -18,6 +18,7 @@ mono
|
||||
|
||||
# Georgy Yakovlev <gyakovlev@gentoo.org> (2020-01-25)
|
||||
# Requires qtwebengine, which is not ported to any of powerpc arches yet
|
||||
pdfium
|
||||
webengine
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2018-09-18)
|
||||
@ -45,10 +46,6 @@ video_cards_amdgpu
|
||||
video_cards_radeonsi
|
||||
clang
|
||||
|
||||
# Jeroen Roovers <jer@gentoo.org> (2015-05-25)
|
||||
# PowerPC has no support for this bootloader (bug #550322)
|
||||
gnuefi
|
||||
|
||||
# These flags should only be used for ppc
|
||||
-cpu_flags_ppc_altivec
|
||||
-cpu_flags_ppc_vsx
|
||||
|
||||
@ -1,13 +1,9 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# This file requires eapi 5 or later. New entries go on top.
|
||||
# Please use the same syntax as in use.mask
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-01-27)
|
||||
# Qt6 is not stable here yet
|
||||
qt6
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2018-04-25)
|
||||
# Dropped stable keywords
|
||||
octave
|
||||
|
||||
@ -1,6 +1,10 @@
|
||||
# Copyright 2023-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Eli Schwartz <eschwartz93@gmail.com> (2024-06-05)
|
||||
# tests require pytest-qt which is not keyworded
|
||||
app-portage/elogviewer test
|
||||
|
||||
# Eray Aslan <eras@gentoo.org> (2024-03-08)
|
||||
# mongodb dependencies are not keyworded
|
||||
mail-mta/postfix mongodb
|
||||
@ -20,7 +24,3 @@ app-admin/syslog-ng grpc
|
||||
# Leonardo Hernández Hernández <leohdz172@proton.me> (2023-11-15)
|
||||
# media-libs/shaderc in not keyworded
|
||||
media-video/ffmpeg shaderc
|
||||
|
||||
# Rich Freeman <rich0@gentoo.org> (2023-09-13)
|
||||
# Tests require shellcheck which is not currently available
|
||||
sys-process/systemd-cron test
|
||||
|
||||
@ -1,6 +1,19 @@
|
||||
# Copyright 2019-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-15)
|
||||
# Requires unkeyworded dev-qt/qtwebengine (and revdeps)
|
||||
kde-plasma/plasma-nm openconnect
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
app-crypt/pinentry qt6
|
||||
app-office/libreoffice qt6
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-05-19)
|
||||
# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559
|
||||
media-gfx/graphicsmagick jpeg2k
|
||||
|
||||
# Robin H. Johnson <robbat2@gentoo.org) (2024-03-13)
|
||||
# sys-cluster/corosync not yet keyworded, niche use case for mdadm
|
||||
sys-fs/mdadm corosync
|
||||
@ -17,11 +30,6 @@ app-emulation/libvirt nbd
|
||||
# Unmask only where grub is keyworded
|
||||
sys-kernel/installkernel -grub
|
||||
|
||||
# Leonardo Hernández Hernández <leohdz172@proton.me> (2023-11-22)
|
||||
# media-libs/libdisplay-info (drm) and dev-libs/libliftoff (liftoff)
|
||||
# are only available for amd64, arm64 and riscv
|
||||
>=gui-libs/wlroots-0.17.0 -drm -liftoff
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2023-10-09)
|
||||
# media-libs/shaderc is keyworded here.
|
||||
media-libs/libplacebo -shaderc
|
||||
@ -216,7 +224,6 @@ dev-libs/mongo-c-driver test
|
||||
# LuaJIT does not support riscv
|
||||
app-text/texlive-core luajittex
|
||||
dev-texlive/texlive-basic luajittex
|
||||
dev-texlive/texlive-context luajittex
|
||||
media-gfx/gimp lua
|
||||
www-servers/nginx nginx_modules_http_lua
|
||||
|
||||
|
||||
@ -4,6 +4,10 @@
|
||||
# Unmask the flag which corresponds to ARCH.
|
||||
-riscv
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
kf6compat
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2023-07-11)
|
||||
# Unmask secureboot flag on arches where sbsigntools is keyworded
|
||||
-secureboot
|
||||
@ -22,6 +26,7 @@
|
||||
|
||||
# Yongxiang Liang <tanekliang@gmail.com> (2024-01-16)
|
||||
# Requires qtwebengine, which is not ported to riscv
|
||||
pdfium
|
||||
webengine
|
||||
|
||||
# Marek Szuba <marecki@gentoo.org> (2021-08-14)
|
||||
|
||||
@ -1,6 +1,10 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-05-08)
|
||||
# Requires sys-devel/{clang,llvm}:16.
|
||||
dev-lang/python jit
|
||||
|
||||
# NRK <nrk@disroot.org> (2024-04-08)
|
||||
# media-libs/libraw is not keyworded
|
||||
media-libs/imlib2 raw
|
||||
@ -202,7 +206,7 @@ dev-python/diskcache test
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2020-08-11)
|
||||
# No drivers on this architecture support Vulkan
|
||||
media-libs/mesa vulkan vulkan-overlay zink
|
||||
media-libs/mesa video_cards_zink vulkan vulkan-overlay zink
|
||||
|
||||
# Hans de Graaff <graaff@gentoo.org> (2019-04-08)
|
||||
# Obsolete ruby version, no newer versions keyworded or stable.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
ARCH="sparc"
|
||||
@ -42,3 +42,7 @@ VIDEO_CARDS="fbdev mga r128 radeon"
|
||||
# Enable USE=libtirpc by default, to ease dependency resolution during
|
||||
# the stabilization of glibc-2.26. Bug 657148
|
||||
USE="libtirpc"
|
||||
|
||||
# Hans de Graaff <graaff@gentoo.org> (2024-05-20)
|
||||
# Allow ruby32 stabling: https://bugs.gentoo.org/932285
|
||||
RUBY_TARGETS="ruby31 -ruby32"
|
||||
|
||||
@ -1,6 +1,13 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2024-06-11)
|
||||
# Extensive use of unaligned access, no plans to fix, #636552
|
||||
# https://github.com/memcached/memcached/issues/902
|
||||
net-misc/memcached
|
||||
dev-libs/libmemcached
|
||||
dev-python/pylibmc
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2023-03-07)
|
||||
# Fails tests disastrously. Present evidence of passing test suite
|
||||
# before removing, please.
|
||||
|
||||
@ -1,6 +1,30 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-29)
|
||||
# media-libs/libplacebo is not keyworded here
|
||||
media-video/ffmpeg libplacebo
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-23)
|
||||
# app-crypt/gcr:4[gtk] is not available here
|
||||
app-crypt/pinentry gtk
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2024-06-11)
|
||||
# net-misc/memcached casualties, #636552
|
||||
# https://github.com/memcached/memcached/issues/902
|
||||
dev-python/pylibmc test
|
||||
dev-python/pytest-services test
|
||||
net-ftp/proftpd memcache
|
||||
dev-ruby/dalli test
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-05-19)
|
||||
# media-libs/jasper not yet keyworded here: https://bugs.gentoo.org/921559
|
||||
media-gfx/graphicsmagick jpeg2k
|
||||
|
||||
# Arthur Zamarin <arthurzam@gentoo.org> (2024-05-13)
|
||||
# Requires dev-util/shelltestrunner
|
||||
app-arch/mt-st test
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-04-02)
|
||||
# dev-qt/qtsvg:6 is not keyworded here yet (bug #918896)
|
||||
dev-qt/qtdeclarative:6 svg
|
||||
@ -32,6 +56,7 @@ sys-kernel/installkernel -grub
|
||||
net-libs/pjproject srtp
|
||||
net-misc/asterisk srtp
|
||||
|
||||
# Marek Szuba <marecki@gentoo.org> (2024-04-24)
|
||||
# Sam James <sam@gentoo.org> (2024-01-05)
|
||||
# sys-apps/keyutils not stable here, because of test failures. bug #636252
|
||||
app-benchmarks/stress-ng keyutils
|
||||
@ -39,7 +64,7 @@ app-crypt/mit-krb5 keyutils
|
||||
app-emulation/qemu keyutils
|
||||
net-fs/samba ads
|
||||
net-fs/cifs-utils ads creds pam
|
||||
sys-auth/sssd keyutils
|
||||
>=sys-libs/libblockdev-3.0.0 cryptsetup
|
||||
sys-libs/libnvme keyutils
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-01-02)
|
||||
@ -86,10 +111,6 @@ sys-apps/openrc s6
|
||||
# Qt 6 not keyworded here.
|
||||
dev-build/cmake gui
|
||||
|
||||
# Rich Freeman <rich0@gentoo.org> (2023-09-13)
|
||||
# Tests require shellcheck which is not currently available
|
||||
sys-process/systemd-cron test
|
||||
|
||||
# Sam James <sam@gentoo.org> (2023-07-21)
|
||||
# Requires app-emulation/qemu.
|
||||
sys-kernel/gentoo-kernel test
|
||||
@ -301,7 +322,7 @@ media-libs/libsdl2 fcitx4
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2020-08-11)
|
||||
# No drivers on this architecture support Vulkan
|
||||
media-libs/mesa vulkan vulkan-overlay zink
|
||||
media-libs/mesa video_cards_zink vulkan vulkan-overlay zink
|
||||
|
||||
# Robin H. Johnson <robbat2@gentoo.org> (2020-07-02)
|
||||
# Mask io-uring & zbc pending keywording
|
||||
@ -606,10 +627,6 @@ gnome-base/gnome classic extras
|
||||
# Missing keywords, bug #493156
|
||||
media-libs/libgphoto2 serial
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-11-28)
|
||||
# Missing keywords, bug #492820
|
||||
net-im/telepathy-connection-managers sipe
|
||||
|
||||
# Pacho Ramos <pacho@gentoo.org> (2013-07-20)
|
||||
# Keywords pending, bug #476710
|
||||
>=gnome-base/gnome-extra-apps-3.8 games
|
||||
|
||||
@ -7,7 +7,6 @@ net-print/cups-filters pdf
|
||||
net-print/libcupsfilters pdf
|
||||
net-print/cups-meta pdf
|
||||
|
||||
|
||||
# Sam James <sam@gentoo.org> (2023-12-30)
|
||||
# Qt not marked stable here.
|
||||
app-text/doxygen gui
|
||||
|
||||
@ -4,6 +4,11 @@
|
||||
# Unmask the flag which corresponds to ARCH.
|
||||
-sparc
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2024-06-11)
|
||||
# Extensive use of unaligned access, no plans to fix, #636552
|
||||
# https://github.com/memcached/memcached/issues/902
|
||||
memcached
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-01-27)
|
||||
# Needs bug #918896 for missing Qt6 keywords
|
||||
qt6
|
||||
@ -136,7 +141,6 @@ xfs
|
||||
musepack
|
||||
topal
|
||||
lqr
|
||||
indi
|
||||
chm
|
||||
ebook
|
||||
capi
|
||||
|
||||
@ -4,6 +4,10 @@
|
||||
# This file requires eapi 5 or later. New entries go on top.
|
||||
# Please use the same syntax as in use.mask
|
||||
|
||||
# Hans de Graaff <graaff@gentoo.org> (2024-05-20)
|
||||
# Allow ruby32 stabling: https://bugs.gentoo.org/932285
|
||||
ruby_targets_ruby32
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-03-07)
|
||||
# dev-lang/php:8.2 is not marked stable here yet (bug #920701)
|
||||
php_targets_php8-2
|
||||
|
||||
8
sdk_container/src/third_party/portage-stable/profiles/arch/x86/i486/package.use.mask
vendored
Normal file
8
sdk_container/src/third_party/portage-stable/profiles/arch/x86/i486/package.use.mask
vendored
Normal file
@ -0,0 +1,8 @@
|
||||
# Copyright 2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Ben Kohler <bkohler@gentoo.org> (2024-05-03)
|
||||
# Requires thin-provisioning-tools, which requires rust, which cannot currently
|
||||
# build/install on i486 or any other CPU class lacking sse2.
|
||||
sys-fs/lvm2 thin
|
||||
app-containers/docker device-mapper
|
||||
@ -1,4 +1,4 @@
|
||||
# Copyright 1999-2023 Gentoo Authors
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# All extra USE/etc should be specified in sub-profiles.
|
||||
|
||||
@ -57,8 +57,6 @@ kde-apps/konqueror:5
|
||||
kde-apps/konsolekalendar:5
|
||||
kde-apps/kontact:5
|
||||
kde-apps/korganizer:5
|
||||
kde-apps/ktp-accounts-kcm:5
|
||||
kde-apps/ktp-text-ui:5
|
||||
kde-apps/libksieve:5
|
||||
kde-apps/mailcommon:5
|
||||
kde-apps/messagelib:5
|
||||
@ -66,7 +64,6 @@ kde-apps/mbox-importer:5
|
||||
kde-apps/parley:5
|
||||
kde-apps/pim-data-exporter:5
|
||||
kde-apps/pim-sieve-editor:5
|
||||
kde-apps/plasma-telepathy-meta:5
|
||||
kde-misc/kio-gdrive
|
||||
kde-misc/tellico:5
|
||||
kde-misc/zanshin:5
|
||||
@ -74,7 +71,6 @@ media-gfx/digikam:5
|
||||
media-gfx/luminance-hdr
|
||||
media-sound/frescobaldi
|
||||
media-sound/teamspeak-client:3
|
||||
media-video/openshot
|
||||
net-analyzer/nmapsi
|
||||
net-libs/signon-ui
|
||||
sci-geosciences/qmapshack
|
||||
|
||||
@ -1,6 +1,11 @@
|
||||
# Copyright 1999-2019 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Ben Kohler <bkohler@gentoo.org> (2024-06-12)
|
||||
# Disable thin volume support by default since it reuqires sse2 which most
|
||||
# x86 cpus will lack
|
||||
sys-fs/lvm2 -thin
|
||||
|
||||
# Ben Kohler <bkohler@gentoo.org> (2022-06-07)
|
||||
# Enable BIOS target by default
|
||||
sys-apps/memtest86+ bios32
|
||||
|
||||
@ -1,22 +1,19 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
app-crypt/pinentry qt6
|
||||
app-office/libreoffice qt6
|
||||
|
||||
# José de Paula R. N. Assis <espinafre@gmail.com> (2024-03-25)
|
||||
# No PyQt6 (which is needed by USE=qt6 for qscintilla-python) on x86.
|
||||
>=dev-python/qscintilla-python-2.14.1-r1 qt6
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-03-24)
|
||||
# Requires unkeyworded dev-qt/qtwebengine
|
||||
net-p2p/ktorrent rss
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-21)
|
||||
# virt-firmware is keyworded here
|
||||
sys-kernel/installkernel -efistub
|
||||
|
||||
# Guilherme Amadio <amadio@gentoo.org> (2024-03-09)
|
||||
# Qt6 not keyworded on x86
|
||||
sci-physics/root qt6
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-03-04)
|
||||
# Miscompiles rust and fails to bootstrap (bug #923278)
|
||||
>=dev-lang/rust-1.74.1 lto
|
||||
@ -86,10 +83,6 @@ net-libs/pjproject webrtc
|
||||
# Needs x11-drivers/nvidia-drivers which is no longer available here.
|
||||
media-tv/mythtv nvdec
|
||||
|
||||
# Craig Andrews <candrews@gentoo.org> (2023-03-09)
|
||||
# media-libs/libplacebo is keyworded here
|
||||
media-video/ffmpeg -libplacebo
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2023-02-06)
|
||||
# Successful build of dev-qt/qtwebengine depends on 64-bit host
|
||||
# Bug #893234
|
||||
@ -103,15 +96,13 @@ kde-apps/kdenetwork-meta bittorrent
|
||||
kde-apps/kleopatra pim
|
||||
kde-apps/umbrello php
|
||||
kde-misc/kio-gdrive share
|
||||
kde-plasma/plasma-nm openconnect
|
||||
net-irc/quassel urlpreview
|
||||
net-misc/fatrat bittorrent
|
||||
net-misc/seafile-client shibboleth
|
||||
net-p2p/ktorrent rss
|
||||
sci-mathematics/yacas gui
|
||||
sci-physics/root qt5
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2022-11-16)
|
||||
# spirv-llvm-translator is not keyworded x86.
|
||||
dev-libs/libclc spirv
|
||||
sci-physics/root qt5 qt6
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2022-11-07)
|
||||
# Vulkan is usable here.
|
||||
|
||||
@ -17,6 +17,14 @@
|
||||
|
||||
#--- END OF EXAMPLES ---
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-04-30)
|
||||
# sys-block/nbdkit is not yet marked stable here
|
||||
app-emulation/libvirt nbd
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2024-04-25)
|
||||
# spirv-llvm-translator is not stable on x86.
|
||||
dev-libs/libclc spirv
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-21)
|
||||
# Experimental, virt-firmware is keyworded only unstable
|
||||
sys-kernel/installkernel efistub
|
||||
|
||||
@ -4,6 +4,10 @@
|
||||
# Unmask the flag which corresponds to ARCH.
|
||||
-x86
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-13)
|
||||
# Needs as-yet-unkeyworded KF6 (bug #934215)
|
||||
kf6compat
|
||||
|
||||
# Paul Zander <negril.nx+gentoo@gmail.com> (2024-04-14)
|
||||
# media-libs/quirc is keyworded on amd64
|
||||
-quirc
|
||||
@ -31,6 +35,7 @@ color-management
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2023-02-06)
|
||||
# Successful build of dev-qt/qtwebengine depends on 64-bit host
|
||||
# Bug #893234
|
||||
pdfium
|
||||
webengine
|
||||
|
||||
# matoro <matoro_gentoo@matoro.tk> (2022-09-29)
|
||||
|
||||
@ -12,10 +12,6 @@ atlas
|
||||
# media-libs/jasper is not stable
|
||||
jasper
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-01-27)
|
||||
# Qt6 is not stable here yet
|
||||
qt6
|
||||
|
||||
# Sam James <sam@gentoo.org> (2020-11-10)
|
||||
# media-gfx/openvdb is not stable on x86
|
||||
# ... and has failing tests right now anyway
|
||||
|
||||
@ -12,7 +12,7 @@ USE_EXPAND_VALUES_KERNEL="Darwin linux SunOS"
|
||||
|
||||
# Env vars to expand into USE vars. Modifying this requires prior
|
||||
# discussion on gentoo-dev@lists.gentoo.org.
|
||||
USE_EXPAND="ABI_MIPS ABI_S390 ABI_X86 ADA_TARGET ALSA_CARDS AMDGPU_TARGETS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_ARM CPU_FLAGS_PPC CPU_FLAGS_X86 CURL_SSL ELIBC FFTOOLS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL L10N LCD_DEVICES LIBREOFFICE_EXTENSIONS LLVM_SLOT LLVM_TARGETS LUA_SINGLE_TARGET LUA_TARGETS MONKEYD_PLUGINS NGINX_MODULES_HTTP NGINX_MODULES_MAIL NGINX_MODULES_STREAM OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PHP_TARGETS POSTGRES_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS RUBY_TARGETS SANE_BACKENDS UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XTABLES_ADDONS"
|
||||
USE_EXPAND="ABI_MIPS ABI_S390 ABI_X86 ADA_TARGET ALSA_CARDS AMDGPU_TARGETS APACHE2_MODULES APACHE2_MPMS CALLIGRA_FEATURES CAMERAS COLLECTD_PLUGINS CPU_FLAGS_ARM CPU_FLAGS_PPC CPU_FLAGS_X86 CURL_SSL CURL_QUIC ELIBC FFTOOLS GPSD_PROTOCOLS GRUB_PLATFORMS INPUT_DEVICES KERNEL L10N LCD_DEVICES LIBREOFFICE_EXTENSIONS LLVM_SLOT LLVM_TARGETS LUA_SINGLE_TARGET LUA_TARGETS MONKEYD_PLUGINS NGINX_MODULES_HTTP NGINX_MODULES_MAIL NGINX_MODULES_STREAM OFFICE_IMPLEMENTATION OPENMPI_FABRICS OPENMPI_OFED_FEATURES OPENMPI_RM PERL_FEATURES PHP_TARGETS POSTGRES_TARGETS PYTHON_SINGLE_TARGET PYTHON_TARGETS QEMU_SOFTMMU_TARGETS QEMU_USER_TARGETS RUBY_TARGETS SANE_BACKENDS UWSGI_PLUGINS VIDEO_CARDS VOICEMAIL_STORAGE XTABLES_ADDONS"
|
||||
|
||||
# USE_EXPAND variables whose contents are not shown in package manager
|
||||
# output. Changes need discussion on gentoo-dev.
|
||||
@ -94,9 +94,9 @@ XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipp2p iface geoip fu
|
||||
LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text"
|
||||
|
||||
# Manuel Rüger <mrueg@gentoo.org> (2015-09-09)
|
||||
# Hans de Graaff <graaff@gentoo.org> (2024-05-20)
|
||||
# Default Ruby build target(s)
|
||||
# Updated to add ruby31 on 2023-05-29 and to drop ruby30 on 2023-06-17
|
||||
RUBY_TARGETS="ruby31"
|
||||
RUBY_TARGETS="ruby31 ruby32"
|
||||
|
||||
# Andreas K. Hüttel <dilfridge@gentoo.org> (2022-10-22)
|
||||
# These USE flags are what is common between the various sub-profiles. Stages 2
|
||||
@ -123,12 +123,13 @@ PYTHONDONTWRITEBYTECODE="1"
|
||||
# This MUST be kept in sync with the PYTHON_TARGETS below
|
||||
# Mike Gilbert <floppym@gentoo.org> (2018-05-23)
|
||||
# sys-apps/baselayout-2.5 needs split-usr enabled.
|
||||
BOOTSTRAP_USE="unicode internal-glib pkg-config split-usr xml python_targets_python3_11 python_single_target_python3_11"
|
||||
# dev-lang/python:3.13 and later needs gil enabled
|
||||
BOOTSTRAP_USE="unicode pkg-config split-usr xml python_targets_python3_12 python_single_target_python3_12 gil"
|
||||
|
||||
# Mike Gilbert <floppym@gentoo.org> (2012-05-15)
|
||||
# Default target(s) for python-r1.eclass
|
||||
PYTHON_TARGETS="python3_11"
|
||||
PYTHON_SINGLE_TARGET="python3_11"
|
||||
PYTHON_TARGETS="python3_12"
|
||||
PYTHON_SINGLE_TARGET="python3_12"
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2013-08-10)
|
||||
# Moved from portage's make.globals.
|
||||
@ -164,7 +165,7 @@ POSTGRES_TARGETS="postgres15"
|
||||
# Moreover, it should only contain targets that have a stable version
|
||||
# of PHP, to avoid pulling in an unstable PHP on stable systems.
|
||||
#
|
||||
PHP_TARGETS="php8-1"
|
||||
PHP_TARGETS="php8-2"
|
||||
|
||||
# Alfredo Tupone <tupone@gentoo.org> (2024-03-15)
|
||||
#
|
||||
|
||||
@ -1,6 +1,13 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-05-30)
|
||||
# Only up to python 3.11 supported, bug #929546
|
||||
<dev-util/kdevelop-python-24.05.1:5 python_single_target_python3_11
|
||||
~www-client/falkon-23.08.5 python_single_target_python3_11
|
||||
dev-python/pyside2 python_targets_python3_11
|
||||
dev-python/shiboken2 python_targets_python3_11
|
||||
|
||||
# Arthur Zamarin <arthurzam@gentoo.org> (2024-03-23)
|
||||
# Used by pkgcheck, so let's make it easier for all developers to install it
|
||||
>=dev-libs/tree-sitter-bash-0.21.0 python
|
||||
|
||||
@ -1,6 +1,22 @@
|
||||
# Copyright 1999-2024 Gentoo Authors
|
||||
# Distributed under the terms of the GNU General Public License v2
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-06-29)
|
||||
# Disabling GIL (enabling freethreading) is experimental and prone
|
||||
# to break packages. Should you choose to test it, please do not file
|
||||
# Gentoo bugs and report any issues you hit upstream.
|
||||
dev-lang/python gil
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-03)
|
||||
# Poor rendering performance otherwise (bug #931215).
|
||||
kde-plasma/kwin caps
|
||||
|
||||
# James Le Cuirot <chewi@gentoo.org> (2024-06-02)
|
||||
# Requires FFmpeg 7.0, which we don't have yet, so force Chromium fork.
|
||||
>=dev-libs/nwjs-0.88.0 ffmpeg-chromium
|
||||
>=www-client/vivaldi-6.8.3371.4 ffmpeg-chromium
|
||||
>=www-client/vivaldi-snapshot-6.8.3371.4 ffmpeg-chromium
|
||||
|
||||
# Ionen Wolkens <ionen@gentoo.org> (2024-04-10)
|
||||
# Flipping the zstd USE state is unsafe and can break *tons* of Qt revdeps
|
||||
# including many KDE packages and Qt itself without rebuilds due to losing
|
||||
@ -174,10 +190,6 @@ net-misc/wget ssl
|
||||
# is maintained for experts only.
|
||||
sys-libs/libcxx libcxxabi
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2019-09-01)
|
||||
# <dev-scheme/guile-2 is package.mask'd, so force USE=guile2
|
||||
media-sound/lilypond guile2
|
||||
|
||||
# Sergei Trofimovich <slyfox@gentoo.org> (2019-08-17)
|
||||
# USE=-cxx us a sure way to break native install as modern gcc
|
||||
# requires C++ to bootstrap. But in rare cases it's useful
|
||||
@ -241,6 +253,7 @@ app-shells/bash:0 readline
|
||||
dev-lang/python-exec python_targets_python3_10
|
||||
dev-lang/python-exec python_targets_python3_11
|
||||
dev-lang/python-exec python_targets_python3_12
|
||||
dev-lang/python-exec python_targets_python3_13
|
||||
dev-lang/python-exec python_targets_pypy3
|
||||
|
||||
# Zac Medico <zmedico@gentoo.org> (2010-10-20)
|
||||
|
||||
@ -6,6 +6,40 @@
|
||||
# This file is only for generic masks. For arch-specific masks (i.e.
|
||||
# mask everywhere, unmask on arch/*) use arch/base.
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-06-29)
|
||||
# JIT is experimental and prone to break packages. Should you choose
|
||||
# to use it, please do not file Gentoo bugs and report any issues you
|
||||
# hit upstream.
|
||||
dev-lang/python jit
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-06-24)
|
||||
# Breaks installed gems in hard-to-debug ways.
|
||||
# bug #887223, bug #891367, bug #903891, bug #917139
|
||||
dev-lang/ruby static-libs
|
||||
|
||||
# Alfredo Tupone <tupone@gentoo.org> (2024-05-28)
|
||||
# Not working, bug #931046
|
||||
>=sci-libs/caffe2-2.3.0 rocm
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-05-09)
|
||||
# Experimental option upstream which seems undertested and underdocumented.
|
||||
# Fails to build with stricter C compilers too (bug #919685).
|
||||
net-misc/openssh xmss
|
||||
|
||||
# Matt Turner <mattst88@gentoo.org> (2024-05-08)
|
||||
# Brand new, introduces lots of new aspects to the build.
|
||||
# Masked for further testing.
|
||||
media-libs/mesa video_cards_nvk
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-04-27)
|
||||
# dev-python/uv is nowhere near ready to be stabilized.
|
||||
dev-python/build test-rust
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-04-23)
|
||||
# app-forensics/libewf is being removed (TestDisk does not build
|
||||
# successfully with our version anyway).
|
||||
app-admin/testdisk ewf
|
||||
|
||||
# Mike Gilbert <floppym@gentoo.org> (2024-04-18)
|
||||
# Wayland client is broken/deprecated by upstream. Bug 930197.
|
||||
>=net-misc/freerdp-3 wayland
|
||||
@ -18,23 +52,10 @@ dev-util/kdevelop reviewboard
|
||||
# sys-auth/pam_ssh is being last rited, bug #892031.
|
||||
sys-auth/pambase pam_ssh
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-03-22)
|
||||
# Building with qt6 requires (masked) kde-frameworks:6
|
||||
app-admin/calamares qt6
|
||||
|
||||
# Viorel Munteanu <ceamac@gentoo.org> (2024-03-19)
|
||||
# The live version needs a new BDEPEND for doc
|
||||
=app-emulation/virtualbox-9999 doc
|
||||
|
||||
# Sam James <sam@gentoo.org> (2024-03-18)
|
||||
# Needs masked KF6 for Wayland at least.
|
||||
app-crypt/pinentry qt6
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-03-17)
|
||||
# Suffers from unaligned accesses, upstream's working on it.
|
||||
# https://github.com/psycopg/psycopg/issues/734
|
||||
<=dev-python/psycopg-3.1.18 native-extensions
|
||||
|
||||
# Guilherme Amadio <amadio@gentoo.org> (2024-03-09)
|
||||
# Requires manually installing dependencies, see bug #791802
|
||||
# Please use MYCMAKEARGS instead.
|
||||
@ -177,7 +198,7 @@ app-admin/ansible-molecule doc
|
||||
# William Hubbs <williamh@gentoo.org> (2023-06-30)
|
||||
# multiple repeated issues: Bug: #909394
|
||||
# Joonas Niilola <juippis@gentoo.org> (2024-04-22)
|
||||
# Can break reverse dependencies (Chromium, Firefox), debugging not always
|
||||
# Can break reverse dependencies (Chromium, Firefox), debugging not always
|
||||
# obvious.
|
||||
net-libs/nodejs lto
|
||||
|
||||
@ -250,10 +271,6 @@ sci-libs/vtk debug
|
||||
# See also: https://bugs.gentoo.org/891499
|
||||
sys-libs/libomp llvm_targets_AMDGPU
|
||||
|
||||
# Sam James <sam@gentoo.org> (2023-01-21)
|
||||
# Fails to compile: https://github.com/libffi/libffi/issues/760
|
||||
<dev-libs/libffi-3.4.4-r4 exec-static-trampoline
|
||||
|
||||
# Joonas Niilola <juippis@gentoo.org> (2023-01-08)
|
||||
# Doesn't compile currently, bug #853094.
|
||||
>=net-dialup/freeradius-3.2.0 oracle
|
||||
@ -271,10 +288,6 @@ app-misc/pax-utils seccomp
|
||||
# Broken when trying to use sys-libs/binutils-libs header, bug #879067
|
||||
>=x11-libs/cairo-1.17.6 debug
|
||||
|
||||
# Joonas Niilola <juippis@gentoo.org> (2022-11-25)
|
||||
# x11-wm/stumpwm-22.05_p20220818[doc] is totally broken. Bug #882935
|
||||
x11-wm/stumpwm doc
|
||||
|
||||
# Bernd Waibel <waebbl-gentoo@posteo.net> (2022-11-25)
|
||||
# USE=tbb is broken in 7.7.0
|
||||
# https://tracker.dev.opencascade.org/view.php?id=33152
|
||||
@ -596,10 +609,6 @@ app-office/abiword ots
|
||||
<sys-devel/clang-17 llvm_targets_Xtensa
|
||||
<sys-devel/llvm-17 llvm_targets_Xtensa
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2020-09-27)
|
||||
# The respective dependencies are masked for removal.
|
||||
net-im/telepathy-connection-managers gadu icq meanwhile steam yahoo
|
||||
|
||||
# Joonas Niilola <juippis@gentoo.org> (2020-09-23)
|
||||
# Highly experimental, may cause breakages when updating. Use with
|
||||
# caution!
|
||||
@ -788,7 +797,6 @@ app-emulation/libvirt openvz
|
||||
# need or even advantage to set custom compiler flags at all.
|
||||
# Example: bug #619628
|
||||
sys-boot/gnu-efi custom-cflags
|
||||
sys-boot/refind custom-cflags
|
||||
|
||||
# Andreas K. Hüttel <dilfridge@gentoo.org> (2017-05-29)
|
||||
# Does not build
|
||||
|
||||
@ -4,10 +4,6 @@
|
||||
# This file requires eapi 5 or later. New entries go on top.
|
||||
# Please use the same syntax as in package.use.force
|
||||
|
||||
# James Le Cuirot <chewi@gentoo.org> (2023-12-23)
|
||||
# Force ffmpeg-chromium fork until ffmpeg-6.1 is stable.
|
||||
www-client/vivaldi ffmpeg-chromium
|
||||
|
||||
## Kent Fredric <kentnl@gentoo.org> (2019-07-11)
|
||||
# The absense of these features require dev-perl/GD, which currently
|
||||
# can't be considered stable due to serious defects upstream.
|
||||
|
||||
@ -4,6 +4,11 @@
|
||||
# This file requires eapi 5 or later. New entries go on top.
|
||||
# Please use the same syntax as in package.use.mask
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-13)
|
||||
# Building with qt6 requires (masked) kde-frameworks:6
|
||||
app-admin/calamares qt6
|
||||
app-crypt/pinentry qt6
|
||||
|
||||
# Andrew Ammerlaan <andrewammerlaan@gentoo.org> (2024-04-14)
|
||||
# Qt6 dependencies are not yet available in stable. Moreover,
|
||||
# Qt6 support in freecad is not completely finished.
|
||||
@ -39,7 +44,6 @@ sci-physics/lammps hip
|
||||
|
||||
# Sam James <sam@gentoo.org> (2022-12-07)
|
||||
# Needs unstable media-libs/libvpl
|
||||
media-libs/gst-plugins-bad qsv
|
||||
media-video/ffmpeg qsv
|
||||
|
||||
# Guillermo Joandet <gjoandet@gmail.com> (2022-11-22)
|
||||
@ -174,10 +178,6 @@ sys-auth/pambase sssd
|
||||
# Needs dev-ruby/asciidoctor which has a lot of unstable deps
|
||||
net-analyzer/wireshark doc
|
||||
|
||||
# Matthias Maier <tamiko@gentoo.org> (2018-03-18)
|
||||
# dev-libs/capstone hasn't been stabilized yet
|
||||
app-emulation/qemu capstone
|
||||
|
||||
# Kent Fredric <kentnl@gentoo.org> (2018-03-03)
|
||||
# Not an officially supported configuration, as it causes unpredictable
|
||||
# fragility and/or dependency headaches due to the very narrow interop window
|
||||
|
||||
@ -4,14 +4,15 @@
|
||||
# This file is only for generic masks. For arch-specific masks (i.e.
|
||||
# mask everywhere, unmask on arch/*) use arch/base.
|
||||
|
||||
# Andreas K. Hüttel <dilfridge@gentoo.org> (2024-05-01)
|
||||
# PERL_FEATURES=debug is not a setting that should be used lightly.
|
||||
# If you really need it, then unmask it...
|
||||
perl_features_debug
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-04-06)
|
||||
# Telepathy is dead and packages masked for removal.
|
||||
telepathy
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2023-12-15)
|
||||
# KF6 is not in ::gentoo yet. Move to stable.use.mask on KF6 intro.
|
||||
kf6compat
|
||||
|
||||
# Hans de Graaff <graaff@gentoo.org> (2023-08-19)
|
||||
# Ruby 3.0 is not compatible with OpenSSL 3. Please upgrade to a newer
|
||||
# Ruby version.
|
||||
|
||||
@ -4,20 +4,25 @@
|
||||
# This file requires eapi 5 or later. New entries go on top.
|
||||
# Please use the same syntax as in use.mask
|
||||
|
||||
# Andreas Sturmlechner <asturm@gentoo.org> (2024-06-13)
|
||||
# KF6 is not in stable yet.
|
||||
kf6compat
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-05-08)
|
||||
# Python implementations without stable keywords.
|
||||
python_targets_python3_13
|
||||
python_single_target_python3_13
|
||||
python_targets_pypy3
|
||||
python_single_target_pypy3
|
||||
|
||||
# Michał Górny <mgorny@gentoo.org> (2024-04-04)
|
||||
# LLVM slots without stablekeywords.
|
||||
llvm_slot_18
|
||||
|
||||
# Hans de Graaff <graaff@gentoo.org> (2023-12-25)
|
||||
# Currently in testing and not ready to go stable yet.
|
||||
ruby_targets_ruby32
|
||||
ruby_targets_ruby33
|
||||
|
||||
# Michael Orlitzky <mjo@gentoo.org> (2023-12-05)
|
||||
# New unstable PHP slot.
|
||||
php_targets_php8-3
|
||||
|
||||
# Zac Medico <zmedico@gentoo.org> (2016-09-01)
|
||||
# Needs dev-python/pypy* stable
|
||||
python_targets_pypy3
|
||||
python_single_target_pypy3
|
||||
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/alpha/23.0/split-usr
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/desktop/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/alpha/23.0/split-usr/desktop
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/alpha/23.0/split-usr/desktop/gnome
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/alpha/23.0/desktop/gnome/systemd
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/developer/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/alpha/17.0/developer/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/alpha/23.0/split-usr
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/alpha/23.0/systemd
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/clang/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/clang/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/musl/llvm
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/musl/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/musl
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/musl/hardened
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/musl/hardened/selinux
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/x32/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.0/x32/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/x32
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/x32/systemd
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/clang/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/clang/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/llvm
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/desktop/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/desktop
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/desktop/gnome
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/desktop/gnome/systemd
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/desktop/plasma
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/desktop/plasma/systemd
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/desktop/systemd
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/developer/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/developer/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/hardened/deprecated
vendored
Normal file
104
sdk_container/src/third_party/portage-stable/profiles/default/linux/amd64/17.1/hardened/deprecated
vendored
Normal file
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/hardened
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
@ -0,0 +1,104 @@
|
||||
default/linux/amd64/23.0/split-usr/hardened/selinux
|
||||
|
||||
A profile upgrade to version 23.0 is available for your architecture.
|
||||
The new 23.0 profiles enable some toolchain hardening features and
|
||||
performance enhancements by default, and standardize settings.
|
||||
You can find the list of changes on the wiki tracking page [1].
|
||||
|
||||
Upgrade instructions
|
||||
|
||||
Note 1: If you have manually changed your CHOST to a value different from
|
||||
what the stages and profiles set, you may have to do that in the future too.
|
||||
In that case you should know what you are doing, hopefully; please read the
|
||||
instructions with a critical eye then.
|
||||
|
||||
Note 2: In case you are already familiar with binary packages, you should be
|
||||
able to add "--getbinpkg" to the emerge calls to speed things up.
|
||||
The use of binary packages is completely optional though, and also not
|
||||
as much tested as the source-based upgrade path yet.
|
||||
|
||||
1. Ensure your system backups are up to date. Please also update
|
||||
your system fully and depclean before proceeding.
|
||||
glibc older than 2.36 and musl older than 1.2.4 is not supported anymore.
|
||||
|
||||
2. If you are still using one of the long-deprecated amd64 17.0 profiles
|
||||
(other than x32 or musl), then first complete the migration to the
|
||||
corresponding 17.1 profile. Instructions can be found at [3].
|
||||
|
||||
3. If you are currently using systemd in a split-usr configuration, then first
|
||||
complete the migration to the corresponding merged-usr profile of the
|
||||
same profile version. Details on how to do this can be found in the news
|
||||
item [4].
|
||||
If you are currently using openrc, migrate to 23.0 first, keeping your disk
|
||||
layout. If you want to move from split-usr to merged-usr, do that afterwards.
|
||||
|
||||
4. Run "emerge --info" and note down the value of the CHOST variable.
|
||||
|
||||
5. Edit /etc/portage/make.conf; if there is a line defining the CHOST variable,
|
||||
remove it. Also delete all lines defining CHOST_... variables.
|
||||
|
||||
6. Select the 23.0 profile corresponding to your current profile, either using
|
||||
"eselect profile" or by manually setting the profile symlink.
|
||||
Note that old profiles are by default split-usr and the 23.0 profiles by
|
||||
default merged-usr. Do NOT change directory scheme now, since this will
|
||||
mess up your system!
|
||||
Instead, make sure that the new profile has the same property: for example,
|
||||
OLD default/linux/amd64/17.1
|
||||
==> NEW default/linux/amd64/23.0/split-usr
|
||||
(added "split-usr")
|
||||
OLD default/linux/amd64/17.1/systemd/merged-usr
|
||||
==> NEW default/linux/amd64/23.0/systemd
|
||||
(removed "merged-usr")
|
||||
A detailed table of the upgrade paths can be found at [5]. Please consult it.
|
||||
In some cases (hppa, x86) the table will tell you to pick between two choices.
|
||||
What you need should be obvious from your *old* CHOST value (from step 4).
|
||||
|
||||
7. Delete the contents of your binary package cache at ${PKGDIR}
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
8. In the file or directory /etc/portage/binrepos.conf (if existing), update
|
||||
the URI in all configuration such that they point to 23.0 profile binhost
|
||||
directories. The exact paths can be found in the table at [5], too.
|
||||
|
||||
9. Rebuild or reinstall from binary (if available) the following packages in
|
||||
this order, with the same version as already active:
|
||||
emerge --ask --oneshot sys-devel/binutils
|
||||
(you may have to run binutils-config and re-select your binutils now)
|
||||
emerge --ask --oneshot sys-devel/gcc
|
||||
(IMPORTANT: If this command wants to rebuild glibc first, do *not* let it do
|
||||
that; instead, abort and try again with --nodeps added to the command line.)
|
||||
(you may have to run gcc-config and re-select your gcc now)
|
||||
and the C library, i.e. for glibc-based systems
|
||||
emerge --ask --oneshot sys-libs/glibc
|
||||
or for musl-based systems
|
||||
emerge --ask --oneshot sys-libs/musl
|
||||
|
||||
10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
|
||||
|
||||
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
|
||||
|
||||
11. Recheck with binutils-config and gcc-config that valid installed versions
|
||||
of binutils and gcc are selected.
|
||||
|
||||
12. Check /etc/env.d, /etc/env.d/binutils, and /etc/env.d/gcc for files that
|
||||
refer to the *OLD* CHOST value, and remove them.
|
||||
Examples how to do this can be found in the similar procedure at [6].
|
||||
|
||||
13. Run env-update && source /etc/profile
|
||||
|
||||
14. Re-emerge libtool:
|
||||
emerge --ask --oneshot libtool
|
||||
|
||||
15. Just for safety, delete the contents of your binary package cache at
|
||||
${PKGDIR} again:
|
||||
rm -r /var/cache/binpkgs/*
|
||||
|
||||
16. Rebuild world:
|
||||
emerge --ask --emptytree @world
|
||||
|
||||
[1] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
|
||||
[2] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
|
||||
[3] https://www.gentoo.org/support/news-items/2019-06-05-amd64-17-1-profiles-are-now-stable.html
|
||||
[4] https://www.gentoo.org/support/news-items/2022-12-01-systemd-usrmerge.html
|
||||
[5] https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_table
|
||||
[6] https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable#Verifying_things_work
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user