This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH] Deprecate libcrypt and don't build it by default.
On Tue, Aug 29, 2017 at 4:58 PM, Joseph Myers <firstname.lastname@example.org> wrote:
> On Tue, 29 Aug 2017, Zack Weinberg wrote:
>> On Tue, Aug 29, 2017 at 4:16 PM, Joseph Myers <email@example.com> wrote:
>> > I don't believe libxcrypt's claim to be a binary-compatible replacement
>> > for libcrypt.so.1. It looks to me like it uses symbol version GLIBC_2.0
>> > unconditionally for the glibc symbols,
>> Well, that's just a plain old bug. Obviously a bug that needs to be
>> fixed before we can call libxcrypt a binary-compatible drop-in
>> replacement, but not a _difficult_ bug - they can crib from the
>> libcrypt.abilist files. I'm willing to try to work up a patch if
>> Björn agrees.
> I'm not convinced that duplicating all the information about which ABIs
> use which symbol versions, and how to distinguish different ABIs on each
> architecture that has ABIs with different base versions, is a good idea.
The plan would be to remove libcrypt from glibc one or two releases
after this deprecation, so it's not so much _duplicating_ the
information as _moving_ it.