Re: [orca-list] Current Orca Version?

[Steve Holmes <steve holmes88 gmail com>]

I suppose the relative numbers are OK to identify git versions but I
see no association between something like 6099+G776 and 3.15.1pre. I
think that's why I prefer sticking to what comes from the 'git
describe' command. I've seen versioning like this with some SVN
projects too and again, I can't relate those version numbers with
actual versioning of the original package itself.

Anyway, just my thoughts on the subject.

On Tue, Oct 28, 2014 at 12:19:07PM +0100, Peter V??gner wrote:
> Heh, this is getting a bit funny.
> I am trying to persuade Steve to change PKGBUILD script so it will no longer
> use git describe since it is not accurate enough at this time. Now Luke is
> highlighting this functionality.
>
> Greetings
>
> Peter
>
>
> On 27.10.2014 at 23:04 Luke Yelavich wrote:
> > On Sun, Oct 26, 2014 at 03:59:17PM AEDT, Steve Holmes wrote:
> > > Thanks for the alternative version segments. Frankly, I think I prefer
> > > the form 3.99.1.... but it would be nice of the git tags represented
> > > the 3.15.1pre but I guess there isn't a way to do that from git at
> > > this time. Anyway, I'll save this message for future use in case this
> > > other format becomes more desirable. I just never found the more
> > > abstract numbering approach always seemed less relevant to me. It's
> > > pretty cool how we can automate the git pull versioning in our
> > > PKGBUILD's now.
> > > Hey, at least I'm getting the latest pull and that is all fine. That's
> > > what mainly matters here.
> > I recently changed Speech Dispatcher to using a script that constructs a version string from the use of 
> > git describe. IMO I think it would be useful if GNOME, or at least Orca, did something similar. It would 
> > have the following advantages, and maybe more I haven't thought of.
> >
> > * Maintainers like joanie would not have to set a pre version string after every upload.
> > * People could pull and build snapshots of git trees without ever having to worry about the version 
> > string, whether it was greater, less than the previous version, etc.
> >
> > Only downside is that the tag format would have to change. Currently the tags are along the lines of 
> > ORCA_3_14_0, which is frankly a pain if one is wanting to look at the log of commits between tags, or 
> > since a tag, so changing the tag format is probably a good thing. :)
> >
> > For those who are unaware, git describe allows you to construct a version string based on the last tag, 
> > and the number of commits since that tag.
> >
> > 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
>
> _______________________________________________
> 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