Dear Gnulib developers, Le dimanche 21 avril 2024 à 06:52 -0400, Bruno Haible a écrit : > If you are developer on a package that uses GNU gnulib as part of its > build > system:
I have a very simple personal project using gnulib. > 1. Make sure you have Python (version 3.7 or newer) installed on your > machine. > > 2. Update your gnulib checkout. (For some packages, it comes as a git > submodule named 'gnulib'.) > > 3. Set an environment variable that enables checking that the two > implementations behave the same: > > $ export GNULIB_TOOL_IMPL=sh+py > > > 4. Clean the built files of your package > > 5. Regenerate the fetched and generated files of your package. > Depending on > the package, this may be a command such as > > $ ./bootstrap --no-git --gnulib-srcdir=$GNULIB_SRCDIR > > If there is a failure, due to differences between the 'sh' and > 'py' > results, please report it to <bug-gnulib@gnu.org>. There are no failures. > The rewritten gnulib-tool was implemented by Dmitry > Selyutin, Collin Funk, and me. You worked well, thank you. Best regards, Vivien
