Hello, Please excuse me if this is not relevant. I'm only trying to help. The version definition can be done in configure.ac, but if you use git, and especially git tags (full tags, i.e. signed: this is important), there is a little-known script named git-version-gen that computes the git version from: 1. The git tags, commit hash, number of commits since the tags, and whether the code corresponds to a clean commit; 2. A ".version" file; 3. A ".tarball-version" that is added so that the version can be used even in a distribution. You can get a copy of the script through gnulib, it is named "git-version-gen". It contains instructions in the script file for how to add it to the project. So if this is not what you want, maybe you could mimic that script to define your package version otherwise. Best regards, Vivien > > If the above is right and if to use its point of view I wonder if some `automake` macro instead of `autoconf` macro > > `AC_INIT` was not a more natural location for package version number specification. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
