Re: [Bug-gnulib] xalloc module dependencies

[Gary V. Vaughan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gary V. Vaughan wrote:
| On a related note (I'm thinking of porting libltdl to gnulib), libltdl has
| implementations of strcmp, strchr and strrchr (presumably from bcmp, index
| and rindex days).  Should I submit them for inclusion in gnulib, or do all
| gnulib supported systems provide their own?

It appears that all of the sources in gnulib are GPL :-(  libltdl is currently
LGPL.  Would there be any interest in my submitting the LGPL versions of the
portability functions libltdl uses for inclusion in gnulib alongside their GPL
namesakes?  The toplevel README implies that this was once a goal of the
project.  On the other hand, it seems painful to maintain 2 versions...

If we merge the improvements of, say, GPL memset.c into my LGPL memset.c, can
we throw away the GPL file and distribute the merge under the LGPL?  I don't
want to stop people from upgrading to the next release of libtool just because
some bits of infrastructure force me (and hence them) to change to GPL.

Is there a way around this, or do I have to continue to maintain my less well
deployed and debugged portability layer to retain LGPL terms for libltdl?  The
silly thing is that many of these functions comprise just a handful of lines
of code each!

Cheers,
        Gary.
- --
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAauViFRMICSmD1gYRAjG8AJ0VhYVplQVNJaJEiexKxY5GGONFEQCdG5s0
kDBjzF090y5omSOK5XagIjE=
=5kr9
-----END PGP SIGNATURE-----