Best practice question

Best practice question

[D. Stuart Freeman]

[-- Attachment #1: Type: text/plain, Size: 248 bytes --]

My project has an "about" page that lists the version.  I understand why
git doesn't do keyword expansion, but I'm wondering if there's a
recommended best practice for keeping that up to date.

-- 
D. Stuart Freeman
Georgia Institute of Technology

[-- Attachment #2: stuart_freeman.vcf --]
[-- Type: text/x-vcard, Size: 162 bytes --]

begin:vcard
fn:D. Stuart Freeman
n:Freeman;Douglas
email;internet:stuart.freeman@et.gatech.edu
tel;work:(404)385-1473
x-mozilla-html:FALSE
version:2.1
end:vcard

Re: Best practice question

[Karl Hasselström]

On 2008-06-19 10:32:35 -0400, D. Stuart Freeman wrote:

> My project has an "about" page that lists the version. I understand
> why git doesn't do keyword expansion, but I'm wondering if there's a
> recommended best practice for keeping that up to date.

Usually when people ask this question on this list, the recommendation
is to have the build system generate a suitable version string. Look
at how git's own built-in version string is generated, for example.
(The GIT-VERSION-GEN script.)

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle

Re: Best practice question

[Santi Béjar]

On Thu, Jun 19, 2008 at 16:32, D. Stuart Freeman
<stuart.freeman@et.gatech.edu> wrote:
> My project has an "about" page that lists the version.  I understand why
> git doesn't do keyword expansion, but I'm wondering if there's a
> recommended best practice for keeping that up to date.

You can look at how git does it:
It generates a GIT-VERSION-FILE with:

http://git.kernel.org/?p=git/git.git;a=blob;f=GIT-VERSION-GEN;hb=HEAD

and reads it in the Makefile. Or you could generate a version.h file.

Santi

Re: Best practice question

[Avery Pennarun]

On 6/19/08, D. Stuart Freeman <stuart.freeman@et.gatech.edu> wrote:
> My project has an "about" page that lists the version.  I understand why
>  git doesn't do keyword expansion, but I'm wondering if there's a
>  recommended best practice for keeping that up to date.

If you compile git yourself and run "git --version", it contains the
current version number.  You may want to do it the same way.

See also the "git-describe" command.

Have fun,

Avery