Re: [orca-list] Current Orca Version?
- From: Luke Yelavich <themuso ubuntu com>
- To: orca-list gnome org
- Subject: Re: [orca-list] Current Orca Version?
- Date: Tue, 28 Oct 2014 09:04:15 +1100
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
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]