From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) by sourceware.org (Postfix) with ESMTP id 2D3F33858025; Fri, 14 Jul 2023 06:26:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2D3F33858025 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gentoo.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gentoo.org References: <20230629184156.2789945-1-siddhesh@sourceware.org> <20230629184156.2789945-5-siddhesh@sourceware.org> User-agent: mu4e 1.10.4; emacs 29.0.92 From: Sam James To: Siddhesh Poyarekar Cc: libc-alpha@sourceware.org Subject: Re: [PATCH 4/4] configure: Disable building libcrypt by default Date: Fri, 14 Jul 2023 07:21:56 +0100 In-reply-to: <20230629184156.2789945-5-siddhesh@sourceware.org> Message-ID: <87zg3z1019.fsf@gentoo.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Siddhesh Poyarekar via Libc-alpha 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! >=20=20 > +* 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.) > - --disable-crypt do not build nor install the passphrase hashing > - library, libcrypt > + --enable-crypt build and install the passphrase hashing libra= ry, > + libcrypt "build and install the deprecated ..." (legacy is fine too, if you like) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZLDqk18UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZC40gEAzfL2qNyPATT8wwSt6Blqe5iqXmHO3LeJ/WGL E0FKI0cA/iH9iQYgx1AOb+IsEavXmlqZJD33cUiCxcEdvDSJxWkI =bUZk -----END PGP SIGNATURE----- --=-=-=--