The script looks in the top level of the Xastir source tree being built for the presence of a .git directory. The fact that the source tree is under a package directory that is itself in git should have no impact (there will then be a .git directory at a higher level, and our script will simply be unaware of it and return no SHA at all).
Our set up has been designed to work under the normal assumption that package maintainers aren't using snapshots, and only will use formal releases (an assumption that has held up for as long as Xastir has existed). It has always been assumed that anyone using the development branch is a power user building it themselves. On Sun, Feb 23, 2020 at 07:14:59PM +0100, we recorded a bogon-computron collision of the <m...@debian.org> flavor, containing: > Re: Tom Russo 2020-02-23 <20200223174551.gd5...@bogodyn.org> > > That won't work if you're building the Debian package > > out of a tarball (the trick involves looking for a .git directory, and if > > found, invoking a git log command to get the current SHA-1). > > Fwiw, these tricks are often a PITA for package maintainers, because > we keep the packaging also in a git repository, but that one doesn't > have any (git) connection to the upstream xastir.git. > > In many cases, we have to patch the build system not to do these > tricks. (Generally, I didn't check if the variant used in xastir is > problematic.) > > Christoph -- Tom Russo KM5VY Tijeras, NM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]