On Thu, May 19, 2022 at 4:49 PM Patrice Dumas <[email protected]> wrote: > > On Thu, May 19, 2022 at 08:05:00AM +0000, Ilari Jääskeläinen wrote: > > Can you include ”autogen.sh” in release source tarballs? > > That looks ok to me. I just checked that ./autogen.sh seems to be > working ok from the release tarball.
What would be the purpose of this? Why run autogen.sh if not building from the git repository? > > Of which ”autogen.sh” should also be capable of regenerating ”gnulib” from > > ”$GNULIB_SRCDIR”, much like GNU Gettext does? > > I do not like that idea. autogen.sh should not do something like that, > should not change code, in my opinion. In README-hacking there is an > explanation on how to rerun gnulib-tool, it is a one liner, I am not > convinced that a separate script that uses $GNULIB_SRCDIR instead of a > path on the command line is more useful. > > We could still add the one liner in a separate script to regenerate > gnulib from $GNULIB_SRCDIR in the util/ directory. gnulib updates are only done occasionally and they often lead to breakages on various platforms when done. I usually only do gnulib updates when a new release is coming up and testing on multiple platforms is being done.
