Then the git sha displayed in Xastir will be the git sha in your package
repo. That is probably OK, though, and will accurately reflect its status
in your package management system.
If you want the About box to have the SHA-1 in our repo, you should just
hack XastirGitStamp to display our SHA-1
Re: Tom Russo 2020-02-23 <20200223182310.ga7...@bogodyn.org>
> 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
>
BTW, since you have chosen to use a snapshot rather than a release, you might
want a later snapshot than the commit bb66a77 you're using. Commit f89c610
(29 Dec 2019) fixed a serious bug in weather alert parsing that had been
introduced in commit aafbc49 (9 May 2019) and which still exists in
Hi Tom,
My apologies for the issues the patch to AC_INIT caused with TOCALL and
thank you for the explanation of versioning semantics. It was a bad
assumption on my part, carried over from $dayjob, when I didn't see a
release tag for 2.1.5 in the repo. 100% my mistake.
Also, thank you to Iain
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
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
This is a forwarded version of an email sent to the Xastir mailing list.
I am forwarding to you because you followed up to a different message on that
list.
To answer your direct question, "Since we are
building from a snapshot - i.e., a version somewhere between 2.1.4 and
2.1.5, is there a
If there is a desire to build Xastir for debian from a tarball *AND* get the
git sha into the Help->About box and "xastir -V" output, one could patch
the script "scripts/XastirGitStamp.sh" so that it blindly inserts the SHA-1
you know to be relevant instead of asking Git to provide it. This would
8 matches
Mail list logo
