Bruno Haible <[EMAIL PROTECTED]> writes: > Hi all, > > There was no objection when I said that: the majority of gnulib modules will > migrate from GPLv2+ to GPLv3+ and from LGPLv2+ to LGPLv3+. So I assume we can > go for it in a few days? > > Before that, please mark the modules that you want to stay at the current > license. We can also revert a license change for a module afterwards, if all > contributors agree, but it's easier if it can be done upfront, because then > it's legally a no-op.
I need the following modules to be usable in a LGPLv2 project: Libidn: gettext-h stdint striconv strverscmp Gsasl: base64 crypto/gc crypto/gc-hmac-md5 crypto/gc-hmac-md5-tests crypto/gc-md5 crypto/gc-md5-tests crypto/gc-random crypto/gc-tests getline gettext maintainer-makefile strdup strverscmp vasprintf GnuTLS: crypto/gc crypto/gc-arcfour crypto/gc-arctwo crypto/gc-des crypto/gc-hmac-md5 crypto/gc-md2 crypto/gc-md4 crypto/gc-md5 crypto/gc-pbkdf2-sha1 crypto/gc-random crypto/gc-rijndael crypto/gc-sha1 getpass gettext memmem memmove minmax read-file snprintf socklen stdint strverscmp sys_socket sys_stat time_r unistd vasprintf Libntlm: check-version des des-tests maintainer-makefile md4 md4-tests strdup strverscmp unistd I'm not sure about libidn, I haven't been following whether glibc is going to be upgraded to LGPLv3 or not. Will it? Libidn is part of libc, so it makes sense for it to use only LGPLv2 helpers if glibc will remain LGPLv2. I moving today, so I don't have time to go through them and check who is the owner etc. I'll see if I find time later this week. Unless someone else beats me to it... /Simon
