(moving to bug-gnulib) Collin Funk <collin.fu...@gmail.com> writes:
> On 3/22/24 2:18 PM, Simon Josefsson wrote:
>> Upgrading inetutils to use gnulib-tool.py would be nice. As a start, I
>> bumped the gnulib submodule.
>
> Bruno and I are still working on it with a test suite. We want the
> file output and stdout output to be the same before we recommend using
> it. Then we won't get many bug reports for the same issue and we can
> test that new changes don't break expected behavior.
>
> With that in mind, I was curious to see how it worked and figured I
> should share.
Thank you!
Is there a way to opt-in inetutils to prefer python gnulib-tool, before
gnulib as a whole changes its default behaviour? I think doing that
will allow better testing of gnulib-tool.py in the wild until gnulib as
a whole can change. This way, we can migrate a bunch of projects to
gnulib-tool.py and get real-world testing of how it works over time for
many months. I would be happy to do this for a bunch of projects
(libidn, libidn2, oath-toolkit, inetutils, libtasn1, gsasl, libntlm,
etc). Maybe this was already discussed and I forgot.
Hmm. Could putting the following into bootstrap.conf be a method that
we could recommend? Then developers can override it with
GNULIB_TOOL_IMPL=sh ./bootstrap if they want.
GNULIB_TOOL_IMPL=${GNULIB_TOOL_IMPL:-py}
/Simon
signature.asc
Description: PGP signature
