-----BEGIN PGP SIGNED MESSAGE-----
Am Mo den 2. Mai 2016 um 18:46 schrieb Colin Clark:
> I think people may try to keep up to date by downloading the master
> rather than wait for a release, but that gives a problem when they
> report problems - what have they compiled?.
> Is it a simple thing to use git hooks to run a command to update a file
> in the repo at each commit, so that the About window can show not just
> major/minor version, but also e.g. the output of "git describe" at the
> time the last commit was made?
Am Mo den 2. Mai 2016 um 18:53 schrieb Josef Kufner:
> Git hooks are not the right tool for this task. It is better to run `git
> describe` during the build process to generate a version file, which
> will be compiled in and shown by `geeqie --version`.
> It is easy to automatically generate version.h with few #define
> statements or something like that and include it wherever neccessary.
Yes. That is also what I think about that.
But there is a problem when people use the tarbal to build their
So the version has to be in the checked out file. There is some substs
that could be used eventually. But finally it has to be set with
checkin, so a hook. Unfortunately for a hook, every developer has to
have them in all the clones. There is no way to manage them within git.
Nevertheless, it is easy to have just "master" in version information.
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <kl...@ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Charset: ISO-8859-1
-----END PGP SIGNATURE-----
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
Geeqie-devel mailing list