Simon Josefsson wrote:
> Hm, but couldn't gnulib-tool check for both filenames?
>
> E.g., when including lib/foo.c test to see if there is a
>
> $local/lib/foo.c
>
> and then
>
> $local/lib%foo.c
>
> This would give projects an option of whether to use the larger
> hierarchy tree style or simp
Eric Blake <[EMAIL PROTECTED]> writes:
>> Generally, I'm not in favour of such a shortcut, because
>> - the gain is small, and it's usually better to have just one way
>> to achieve a certain functionality rather than two (because each
>> of the two will be less well tested than the comm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 7/5/2007 4:20 AM:
>
> This is a bit better, but maybe '%' or ':' are better separators.
'%', maybe. ':', absolutely not. Using a colon will foul up CVS
checkouts to picky file systems (such as anything on Windows).
>
Eric Blake wrote:
> For an example, with
> just gpl-3.0.texi.diff and version-etc.c.diff, the difference is between:
>
> --local-dir=local
> local/lib/version-etc.c.diff
> local/doc/gpl-3.0.texi.diff
>
> or
>
> --local-dir=local
> local/version-etc.c.diff
> local/gpl-3.0.texi.diff
The latter in
Eric Blake <[EMAIL PROTECTED]> writes:
> --local-dir=local
> local/lib/version-etc.c.diff
> local/doc/gpl-3.0.texi.diff
>
> or
>
> --local-dir=local
> local/version-etc.c.diff
> local/gpl-3.0.texi.diff
How about:
local/lib_version-etc.c.diff
local/doc_gpl-3.0.texi.diff
or
local/lib+version-etc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just modified M4 to use gnulib-tool --local-dir in order to upgrade M4
to GPLv3 (the version-etc module still prints GPLv2+ without a local
patch) [1]. However, I noticed that gnulib-tool currently requires that
.diff files be laid out in the same d
