Re: [orca-list] Git Version in Master?

[Peter Vágner <pvdeejay gmail com>]

Hello,
Perhaps you might consider changing your PKBUILD version string then.
I suggest something like

pkgver() {
    cd ${pkgname}
    echo $(git rev-list --count HEAD)+g$(git rev-parse --short HEAD)
}

What will output something like
6745+gbea2900
We will get increasing number as the new commits are added and we will 
be able to identify the commit the resulting build corespond with. And 
it does not contain package name plus other over ververbosed bits from 
the description.

Greetings

Peter

On 30.04.2014 06:41, Luke Yelavich wrote:
> On Wed, Apr 30, 2014 at 01:49:20PM EST, Steve Holmes wrote:
> > I see that the master version of Orca says 3.13pre1 but when I do a
> > 'git describe' after the most recent git pull, I get
> > ORCA_3_11_90-102-gacb131f. My package build script for the Arch Linux
> > orca-git package uses this command to automatically determine the
> > correct orca version. Is there a reason git still thinks master is in
> > the 3.11.90 range rather than something like 3.13?
> Orca 3.12 was branched before the 3.12 tag was created. If you were to run the same command in the 3.12 
> branch, you would get the 3.12 tag as the base of the output from git describe.
>
> I would have thought 3.12 branch would have been done once the 3.12 release was tagged in master, but I guess 
> we all work differently. :)
>
> Luke
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp