[WIP] New package: libxcrypt-4.4.33 #41431
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Testing the changes
libxcrypt will replace libcrypt on glibc.
--disable-failure-tokens
as per:besser82/libxcrypt#25
glibc will need to be compiled with
--disable-crypt
.musl provides no such option, Debian just rm's libcrypt.a from musl:
https://salsa.debian.org/reiner/musl/-/blob/master/debian/rules#L76
Not sure what we want to do on musl.
For glibc either we can rebuild everything with libxcrypt or we can have glibc depend on libxcrypt-compat (and have libxcrypt as a bootstrap package)
On musl, libcrypt is provided by libc so if we handle it the same as debian, a rebuild shouldn't be necessary.
All packages using libcrypt can be seen using
xbps-query -Rs libcrypt.so -p shlib-requires
.