mirror of
https://github.com/flatcar/scripts.git
synced 2025-09-25 07:31:01 +02:00
overlay profiles: Migrate from glibc crypt to libxcrypt
It's long overdue and glibc 2.39 will drop crypt stuff altogether. Or so I heard. Whatever happens, the crypt library in glibc is deprecated for a long time already.
This commit is contained in:
parent
0c8a60e78a
commit
5b64defa98
@ -11,12 +11,6 @@
|
||||
# certificate store provided in NSS rather than the Gentoo/Debian package.
|
||||
>=app-misc/ca-certificates-20000000
|
||||
|
||||
# Overwrite portage-stable mask. We are delaying the transition to
|
||||
# libxcrypt, because we need to figure out how to solve the dep loop
|
||||
# that results from the migration (python -> virtual/libcrypt ->
|
||||
# libxcrypt -> glibc -> python).
|
||||
>=virtual/libcrypt-2
|
||||
|
||||
# Python 3.12 is in portage-stable (currently testing), so avoid picking it
|
||||
# up. Update this to mask later versions when we switch to 3.11.
|
||||
>=dev-lang/python-3.12
|
||||
|
@ -1,9 +1,3 @@
|
||||
# Overwrite portage-stable mask. We are delaying the transition to
|
||||
# libxcrypt, because we need to figure out how to solve the dep loop
|
||||
# that results from the migration (python -> virtual/libcrypt ->
|
||||
# libxcrypt -> glibc -> python).
|
||||
<virtual/libcrypt-2
|
||||
|
||||
# Overwrite portage-stable mask. We haven't seen LLVM related problems
|
||||
# with rust so far, so keep using 1.70.0.
|
||||
~dev-lang/rust-1.78.0
|
||||
|
@ -14,10 +14,6 @@ app-alternatives/sh bash
|
||||
app-alternatives/tar gnu
|
||||
app-alternatives/yacc bison
|
||||
|
||||
# Force libcrypt so it's included in stage-1 of the SDK build.
|
||||
# +crypt was introduced in glibc-2.30 and above.
|
||||
sys-libs/glibc crypt
|
||||
|
||||
# Do not force this flag, we don't need XATTR_PAX
|
||||
sys-apps/portage -xattr
|
||||
|
||||
|
@ -17,13 +17,6 @@ sys-libs/ncurses cxx
|
||||
# which is defined in portage-stable.
|
||||
app-editors/nano unicode
|
||||
|
||||
# Overwrite portage-stable mask. We are delaying the transition to
|
||||
# libxcrypt, because we need to figure out how to solve the dep loop
|
||||
# that results from the migration (python -> virtual/libcrypt ->
|
||||
# libxcrypt -> glibc -> python), and also we need to update gcc to
|
||||
# version 10 or later.
|
||||
sys-libs/glibc -crypt
|
||||
|
||||
# We don't use pip.
|
||||
dev-lang/python ensurepip
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user