> Yes, that's true. But on the other hand, otherwise there would no
> explanation for bootstrap's attempt to checkout gnulib itself, no? :-)
>
> [...]
>
> bootstrap is meant for people who checked out your project from VCS, so
> that they do not need to know about gnulib at all. You do not need t
> + Would it not result in unnecessary commits to the SCM to keep it
> synchronized with Gnulib's version?
Yes, that's true. But on the other hand, otherwise there would no
explanation for bootstrap's attempt to checkout gnulib itself, no? :-)
> + A user who wants to fiddle with the release tar
> I don't think this is how bootstrap is meant to be used. You should
> distribute it together with your application, and do "./bootstrap
> --skip-po --gnulib-srcdir=/devel/gnulib/git/gnulib".
Just as the other files pulled in from Gnulib were not part of the
source tree, bootstrap was also being
Debarshi Ray wrote:
>>> This particular change due to 29dd8b5548ce047ce51ff9a73d6c4b50c9886771
>>> has broken bootstrap for the particular use case where it is invoked
>>> using an absolute path (eg.,
>>> /devel/gnulib/git/gnulib/build-aux/bootstrap --skip-po
>>> --gnulib-srcdir=/devel/gnulib/git/g
>> This particular change due to 29dd8b5548ce047ce51ff9a73d6c4b50c9886771
>> has broken bootstrap for the particular use case where it is invoked
>> using an absolute path (eg.,
>> /devel/gnulib/git/gnulib/build-aux/bootstrap --skip-po
>> --gnulib-srcdir=/devel/gnulib/git/gnulib):
> How does it fa
Debarshi Ray wrote:
> This particular change due to 29dd8b5548ce047ce51ff9a73d6c4b50c9886771
> has broken bootstrap for the particular use case where it is invoked
> using an absolute path (eg.,
> /devel/gnulib/git/gnulib/build-aux/bootstrap --skip-po
> --gnulib-srcdir=/devel/gnulib/git/gnulib):
>
