libcidn (was: Re: Remove add-ons mechanism)

["Andreas K. Huettel" <dilfridge at gentoo dot org>]

Am Donnerstag, 5. Oktober 2017, 14:54:47 CEST schrieb Joseph Myers:
> On Thu, 5 Oct 2017, Florian Weimer wrote:
> > Their packaging is completely different from the libidn upstream releases.
> 
> And updating from the libidn upstream releases would be problematic given
> that it's a non-FSF-assigned project that has changed license.  (See
> however the idea of enabling glibc to dlopen unmodified upstream libidn to
> implement the functionality that uses glibc's copy of libidn, as a
> possible replacement of that copy.)

I understand...

Mostly out of curiosity, what is the usecase for the glibc-internal libidn?

A quick scan on my laptop (Gentoo Linux) shows no binaries that have 
libcidn.so in NEEDED (but many with the separate libidn.so).

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

Attachment: signature.asc
Description: This is a digitally signed message part.