This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: libidn add-on into main glibc.tar
- From: Simon Josefsson <simon at josefsson dot org>
- To: Roland McGrath <roland at redhat dot com>
- Cc: libc-alpha at sources dot redhat dot com
- Date: Thu, 29 Oct 2009 08:32:03 +0100
- Subject: Re: libidn add-on into main glibc.tar
- Openpgp: id=B565716F; url=http://josefsson.org/key.txt
- References: <20091028234617.3C4584F4@magilla.sf.frob.com>
Roland McGrath <roland@redhat.com> writes:
> I would like to start including the libidn/ add-on directory in the main
> glibc source distribution tar files. Does anyone see a problem with this?
I don't. The libidn copy in libc is rather old, so you might want to
look into syncing the code from the real libidn. On the other hand, I
don't recall any critical fixes in a long time, so it might not be worth
the effort.
> I assume that the reason it's been kept separate before is because of its
> non-FSF copyright owner. I wasn't keeping track of these things at the
> time libidn went into libc. Last time I knew the GNU policy for libc was
> to badly want everything in it FSF-owned. I thought that was GNU policy
> for GNU things generally, but GNU Libidn is a GNU thing now and has that
> copyright owner, so I guess that is OK by GNU.
Yes. I recall discussing this when I started the libidn project and it
was OK. Anyway, I suspect I have a copyright assignment for libc in
place already, and I did the first patch to make libc use libidn, so
this may be a non-issue.
/Simon
> The only practical effect for users would be that unpacking glibc-N.tar
> alone and using configure --enable-add-ons would now catch libidn as well
> as nptl, whereas before tar-unpacking builders would have had to unpack
> glibc-libidn-N.tar too and move it in and/or use --enable-add-ons=blah,blah.
> I assume this is no problem at all for anyone in reality. All hackers who
> build from checkouts and use plain --enable-add-ons get this already.
>
> The reason to want to do this (and now) is that it would let us use a
> simple 'git archive' method for creating the official GNU tar files
> for libc releases.
>
>
> Thanks,
> Roland