Bruno Haible <[EMAIL PROTECTED]> writes:
> The argument for making it LGPL is that an LGPLed package can include
> them without making a complicated license statement like "the library
> source is under LGPL, the testsuite under GPL, and the doc under GFDL".
I'm afraid we've already lost that bat
Under which license should tests module be?
If I have an LGPLed module, should its -tests module be LGPL or GPL?
The argument for making it LGPL is that an LGPLed package can include
them without making a complicated license statement like "the library
source is under LGPL, the testsuite under GP
Test module descriptions don't have a license statement of their own.
When "gnulib-tool --create-testdir --with-tests" is used, it emits a
warning:
warning: module iconv depends on a module with an incompatible license:
iconv-tests
This fixes it.
2007-01-14 Bruno Haible <[EMAIL PROTECTED]>
2007-01-14 Bruno Haible <[EMAIL PROTECTED]>
* modules/iconv (Include): Clarify that can only be included
if iconv is found to exist.
*** modules/iconv 5 Oct 2005 13:21:37 - 1.8
--- modules/iconv 14 Jan 2007 22:17:15 -
***
*** 13,19
M
Simon recently reported that --create-testdir was running configure
when it was not necessary. This fixes it.
2007-01-14 Bruno Haible <[EMAIL PROTECTED]>
* gnulib-tool (func_create_testdir): Don't unnecessarily run configure
and make.
Reported by Simon Josefsson in
On Fri, Jan 12, 2007 at 08:30:24AM -0700, Eric Blake wrote:
> why should you expect sane behavior from tools that assume POSIX?
If xreadlink() assumed POSIX, it would allocate a fixed buffer of 256 bytes.
> By violating that rule of POSIX, the bug is squarely on your FS's shoulders,
I'm not even
Hi,
Since there were no comments about the fchdir module, and I tested it on two
platforms, I committed it.
Paul Eggert wrote:
> I don't know what --avoid=canonicalize-lgpl is for. Perhaps you can
> omit it.
It's because coreutils already uses the 'canonicalize' module, and 'fchdir'
depends on
