This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: What to do about libidn?

From: Carlos O'Donell <carlos at redhat dot com>
To: Florian Weimer <fweimer at redhat dot com>, Joseph Myers <joseph at codesourcery dot com>
Cc: GNU C Library <libc-alpha at sourceware dot org>
Date: Fri, 11 Nov 2016 14:53:54 -0500
Subject: Re: What to do about libidn?
Authentication-results: sourceware.org; auth=none
References: <44cead16-9db0-a4c0-82cd-1f6178260ed7@redhat.com> <alpine.DEB.2.20.1611082325180.23898@digraph.polyomino.org.uk> <9b77b43c-f255-6401-5648-0b5cc405cf4b@redhat.com>

On 11/09/2016 07:02 AM, Florian Weimer wrote:
> In the broader picture, I think we should discourage out-of-tree
> ports and functionality as much as possible because if something is
> not part of regular builds because it's not in the official source
> tree, we might only learn about fundamental incompatibilities after a
> release or two, which would be annoying.  So I'd suggest the remove
> the add-on mechanism eventually.

Agreed.

I would also vote for out-of-tree functionality to be removed.

Users can simply have cloned trees with their own patches, and help
in the overall library maintenance or work with upstream to integrate
their changes.

-- 
Cheers,
Carlos.

References:
- What to do about libidn?
  - From: Florian Weimer
- Re: What to do about libidn?
  - From: Joseph Myers
- Re: What to do about libidn?
  - From: Florian Weimer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]