>> . First of all, there is some user-unfriendliness: Without
>> installing a gnulib submodule for project `foo', just invoking
>> the `bootstrap' script in the `foo' directory' without any
>> arguments gives
>>
>> ./bootstrap: line 610: gnulib/gnulib-tool: No such file or directory
>>
>> This looks like a bug in the script, which it isn't actually.
>> Maybe `bootstrap' can be improved to emit a suggestion how to
>> proceed.
>
> Patches welcome.
Well, it seems there are more problems both with documentation and
probably with the code.
After doing the incantation described in section 2.8 of gnulib.pdf,
namely
$ dir=.gnulib
$ git submodule add -- git://git.sv.gnu.org/gnulib.git $dir
the user has to commit the submodule setup to the repository. It's
probably worth to mention this.
However, if I now say `git config --file .gitmodules --list' (I
haven't touched the data within `.gitmodules'), I see
submodule..gnulib.path=.gnulib
submodule..gnulib.url=git://git.sv.gnu.org/gnulib.git
Note the double dot. Interestingly, the name of the submodule is
taken from the directory location, not the repository name. Maybe a
git bug? I'm using version 1.7.8.
> ./bootstrap --gnulib-srcdir=/path/to/reference
This works fine, thanks.
Werner
