From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [WIP] New package: libxcrypt-4.4.33
Date: Wed, 09 Aug 2023 13:24:48 +0200 [thread overview]
Message-ID: <20230809112448.CVZN0v2gczIfOukhE58szzy8GzKSoAsTpSRWGyEe_Mc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41431@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1827 bytes --]
There's a closed pull request on the void-packages repository
[WIP] New package: libxcrypt-4.4.33
https://github.com/void-linux/void-packages/pull/41431
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **NO**
libxcrypt will replace libcrypt on glibc.
`--disable-failure-tokens` as per:
https://github.com/besser82/libxcrypt/issues/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`.
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
next prev parent reply other threads:[~2023-08-09 11:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 2:05 [PR PATCH] " oreo639
2023-01-04 2:05 ` [PR PATCH] [Closed]: " oreo639
2023-01-04 2:20 ` [PR PATCH] [Updated] [WIP] " oreo639
2023-01-04 2:24 ` oreo639
2023-01-04 2:34 ` oreo639
2023-01-04 3:05 ` oreo639
2023-05-09 1:53 ` github-actions
2023-05-13 4:56 ` oreo639
2023-08-09 11:24 ` oreo639 [this message]
2023-08-09 11:24 ` oreo639
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230809112448.CVZN0v2gczIfOukhE58szzy8GzKSoAsTpSRWGyEe_Mc@z \
--to=oreo639@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).