You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It has been brought to my attention (thanks @troglobit) that some distributions (notably Debian) will always run autoreconf on all packages.
The current flow only considers two scenarios:
Building from git clone. configure must be generated, but .git is available so the version can be found.
Building from release tarball. configure is already generated so it does not matter that .git is missing.
But in order to support regeneration of configure from release tarballs, the version info must be manually managed in configure.ac. Perhaps we can at least work out some way of appending git version info if it is available.
The text was updated successfully, but these errors were encountered:
It has been brought to my attention (thanks @troglobit) that some distributions (notably Debian) will always run
autoreconf
on all packages.The current flow only considers two scenarios:
configure
must be generated, but.git
is available so the version can be found.configure
is already generated so it does not matter that.git
is missing.But in order to support regeneration of
configure
from release tarballs, the version info must be manually managed inconfigure.ac
. Perhaps we can at least work out some way of appending git version info if it is available.The text was updated successfully, but these errors were encountered: