Collin Funk wrote:
> I like the plan of picking ~10 GNU packages and think it is a good
> starting point that we can adjust if needed. Since the process is
> useful for me anyways, I think it is best that go through the list of
> packages in users.txt and try building them.
OK. If you start to go into this direction, it is time for me to
implement the GNULIB_TOOL_IMPL=sh+py option. Done through the patch below.
But in the current state, it fails for nearly every command. There's
no hope that you can expect identical results from the two implementations
as long as there are still items in the TODO list.
> I can keep a file locally and just email it when we are ready for more
> formal testing, or I can keep it in the git repository somewhere.
You can keep such a file locally.
Bruno
2024-03-14 Bruno Haible <br...@clisp.org>
gnulib-tool: Obey environment variable GNULIB_TOOL_IMPL.
* gnulib-tool.sh: Renamed from gnulib-tool.
* gnulib-tool: New file, based on gnulib-tool.sh.
* gnulib-tool.py: Check the Python version.
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=d42c4b5a002f0c9d3960d45510a3cc072799a954
