Simon Josefsson wrote: > > Yes, and I hope that once the approach to let 'git-version-gen' be run > > at configure time (as opposed to autoconf time) is more widely accepted, > > Oh! Is that changed now?
Yes. It should have been clear from the list of fixes [1] and from the new documentation (now published at [2]). > What will VERSION be during autoconf time? What do you mean? How do you want to observe the value of VERSION at autoconf time? There is no documented interface for doing that. > UNKNOWN? I don't yet have an opinion on this, that change seems likely > to cause problems with code that assume VERSION is populated, but it may > also be that all such code is questionable and could be fixed anyway, Code that greps through configure.ac will need to be fixed, yes. It can be fixed and *should* be fixed. Recall that the purpose of 'git-version-gen' is that each time the maintainer makes a commit, the version number changes. It's already much of a burden that 'configure' needs to re-run. But additionally regenerating the 'configure' script is no longer needed. Bruno [1] https://lists.gnu.org/archive/html/bug-gnulib/2025-01/msg00191.html [2] https://www.gnu.org/software/gnulib/manual/html_node/Package-version-management.html
