From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Sam James <sam@gentoo.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 4/4] configure: Disable building libcrypt by default
Date: Mon, 17 Jul 2023 11:24:25 -0400 [thread overview]
Message-ID: <7543593b-0f9e-dc36-86f7-9b61749231b3@sourceware.org> (raw)
In-Reply-To: <87zg3z1019.fsf@gentoo.org>
On 2023-07-14 02:21, Sam James wrote:
>
> Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org> writes:
>
>> We mentioned eventual dropping of libcrypt in the 2.28 NEWS. Actually
>> put that plan in motion by first disabling building libcrypt by default.
>> In the near future we need to drop it completely but ISTM that Gentoo
>> still uses it to fix some perl compatibility issues.
>
> Thanks. This is fine for us: we did the migration in two stages in
> Mid-to-late 2021.
>
> You are right that we've got a workaround for some Perl rebuild issues,
> but that should've been fixed on our end in the package manager last
> month, so no problem from us. Thank you for checking!
>>
>> +* libcrypt is no longer built by default, one may use the --enable-crypt
>> + option to build libcrypt. It is recommended that applications port
>> + away from the GNU C Library implementation of libcrypt since it will
>> + likely be removed in a future release.
>
> I feel like we ought to explicitly name libxcrypt as a possible
> provider - I don't really like relying on word of mouth for this.
>
> We don't need to endorse it/recommend it (although what's the
> alternative?), but I think mentioning it is worthwhile.
>
> (ditto for texi change.)
>
Should we put a date on it, i.e. say explicitly that it will be removed
in 2.39?
Thanks,
Sid
next prev parent reply other threads:[~2023-07-17 15:24 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 18:41 [PATCH 0/4] Update default build configuration Siddhesh Poyarekar
2023-06-29 18:41 ` [PATCH 1/4] configure: Use autoconf 2.71 Siddhesh Poyarekar
2023-06-29 19:48 ` Joseph Myers
2023-06-29 19:56 ` Siddhesh Poyarekar
2023-06-29 20:03 ` Siddhesh Poyarekar
2023-06-29 20:07 ` Joseph Myers
2023-06-29 22:16 ` Zack Weinberg
2023-06-29 18:41 ` [PATCH 2/4] configure: Default --enable-stack-protector to strong Siddhesh Poyarekar
2023-06-29 18:41 ` [PATCH 3/4] Disable lazy binding by default Siddhesh Poyarekar
2023-06-29 21:54 ` Michael Hudson-Doyle
2023-06-29 22:16 ` Siddhesh Poyarekar
2023-06-29 18:41 ` [PATCH 4/4] configure: Disable building libcrypt " Siddhesh Poyarekar
2023-06-29 18:45 ` Dmitry V. Levin
2023-06-29 19:02 ` Siddhesh Poyarekar
2023-07-14 6:21 ` Sam James
2023-07-17 15:24 ` Siddhesh Poyarekar [this message]
2023-07-17 17:26 ` Sam James
2023-06-30 1:42 ` [PATCH v2 0/4] Update default build configuration Siddhesh Poyarekar
2023-06-30 1:42 ` [PATCH v2 1/4] configure: Use autoconf 2.71 Siddhesh Poyarekar
2023-07-14 21:00 ` Carlos O'Donell
2023-07-17 14:21 ` [PATCH v3] " Siddhesh Poyarekar
2023-07-17 14:46 ` Siddhesh Poyarekar
2023-06-30 1:42 ` [PATCH v2 2/4] configure: Default --enable-stack-protector to strong Siddhesh Poyarekar
2023-07-13 9:51 ` Florian Weimer
2023-07-17 14:55 ` Siddhesh Poyarekar
2023-07-17 15:45 ` Florian Weimer
2023-07-17 15:52 ` Siddhesh Poyarekar
2023-08-03 10:06 ` Florian Weimer
2023-06-30 1:42 ` [PATCH v2 3/4] configure: Disable lazy binding by default Siddhesh Poyarekar
2023-07-13 9:38 ` Florian Weimer
2023-07-17 14:57 ` Siddhesh Poyarekar
2023-07-17 15:30 ` Florian Weimer
2023-07-17 15:55 ` Siddhesh Poyarekar
2023-07-18 16:25 ` Andreas K. Huettel
2023-06-30 1:42 ` [PATCH v2 4/4] configure: Disable building libcrypt " Siddhesh Poyarekar
2023-07-13 9:40 ` Florian Weimer
2023-07-14 4:16 ` Mark Harris
2023-07-17 15:13 ` Siddhesh Poyarekar
2023-07-17 16:44 ` [PATCH v3] " Siddhesh Poyarekar
2023-07-17 17:18 ` Andreas Schwab
2023-07-17 18:17 ` Siddhesh Poyarekar
2023-07-20 18:05 ` Joseph Myers
2023-07-20 18:39 ` Andreas K. Huettel
2023-07-07 10:31 ` [ping][PATCH v2 0/4] Update default build configuration Siddhesh Poyarekar
2023-07-12 21:51 ` [ping2][PATCH " Siddhesh Poyarekar
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=7543593b-0f9e-dc36-86f7-9b61749231b3@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=sam@gentoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).