I did:
> 2024-03-17 Bruno Haible
>
> gnulib-tool: Add undocumented option --gnulib-dir.
Two more tweaks are needed for the test suite:
2024-03-19 Bruno Haible
gnulib-tool: Make it work in the test suite.
* gnulib-tool.sh (gnulib_dir): Make
Bruno Haible writes:
> No, what I mean is just to take a snapshot. For the reasons explained in
> https://lists.gnu.org/archive/html/bug-gnulib/2024-03/msg00109.html .
Ah, I see. I misunderstood the "frozen-in-time set of gnulib modules",
but that message explains it. Thanks.
Collin
Hi Collin,
> > The gnulib-tool test suite will need this option, in order to use the
> > newest gnulib-tool with a frozen-in-time set of gnulib modules.
>
> By this do you mean if a project has a old gnulib git submodule? I think
> I ran into this with GNU Bison for example. It hasn't had commits
Hi Bruno,
Bruno Haible writes:
> The gnulib-tool test suite will need this option, in order to use the
> newest gnulib-tool with a frozen-in-time set of gnulib modules.
By this do you mean if a project has a old gnulib git submodule? I think
I ran into this with GNU Bison for example. It hasn't
The gnulib-tool test suite will need this option, in order to use the
newest gnulib-tool with a frozen-in-time set of gnulib modules.
2024-03-17 Bruno Haible
gnulib-tool: Add undocumented option --gnulib-dir.
* gnulib-tool.sh: Accept --gnulib-dir=... option
