This is the mail archive of the
mailing list for the glibc project.
Re: The direction of malloc?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, Roland McGrath <roland at hack dot frob dot com>, Andreas Jaeger <aj at suse dot com>, Andreas Schwab <schwab at suse dot de>, OndÅej BÃlka <neleai at seznam dot cz>, Siddhesh Poyarekar <siddhesh at redhat dot com>, Pavel Simerda <psimerda at redhat dot com>, Roland McGrath <roland at hack dot frob dot com>
- Date: Fri, 13 Dec 2013 18:49:24 -0500
- Subject: Re: The direction of malloc?
- Authentication-results: sourceware.org; auth=none
- References: <52A6A0DA dot 1080109 at redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1312101639060 dot 15324 at digraph dot polyomino dot org dot uk> <52AAE179 dot 9060802 at redhat dot com>
On 12/13/2013 05:29 AM, Florian Weimer wrote:
> On 12/10/2013 05:49 PM, Joseph S. Myers wrote:
>> I don't know about the resolver code from BIND, a substantial body
>> of code that I think*is* maintained upstream of glibc but was last
>> updated from upstream in glibc 2.2 (according to the NEWS file,
> Do you mean netresolv?
> This effort doesn't seem to have materialized yet, and I think ISC's
> 2009 code drop was just extracted unchanged from the unmaintained
> libbind from BIND 8 that still shipped with BIND 9 releases at the
I don't even know how we legally bring in the BIND 9 code.
I see nowhere that it's assigned to the FSF, and it's not LGPLv2.
Some serious legal wrangling would have to be done with the FSF
at each import IMO.
In the past did we just ask the FSF for permission to use the
bind code? How hard was that process?