Re: [orca-list] Current Orca Version?



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.

On Fri, Oct 24, 2014 at 07:41:17PM +0200, Peter V??gner wrote:
Hello,
Several facts:
- Orca development continues in the master branch where new features are
added all the time.
- When you clone the orca git repository and you won't specify a branch to
checkout you will end with master branch in your local tree.
- Other branches are usually created to prepare a stable release. While the
stable release is tested and bugfixed new stuff can be added to the master
branch.
- In all branches including master developers are able to tag specific
commits to easily refer to individual testing releases and / or milestones.
- git describe prints reference to the latest such tag in the current branch
along with the latest commit. I think if you would like to maintain various
orca-git packages where major version differ you can create multiple
packages pulling different tags from the respective branches.
- Since there is no easy way to accuratelly retrieve the orca version from
git you can just version your package incrementally always checking out from
the master branch. This is what is verry common and people are used to it.
Here are two example functions you may wish to add into your PKGBUILD file.
It does not matter too much what you will end up with as long as you like it
and it increments with each update.

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

pkgver() {
  cd "${pkgname}"
  printf "r%s.g%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short
HEAD)"
}




On 24.10.2014 at 13:23 Steve Holmes wrote:
Well, since I maintain the AUR PKGBUILD for orca-git, I need to figure
out a different way to retrieve the current and correct version number
when pulling from git.

Also, I wasn't aware of different branches in git right now. I did not
see these other branches when I listed them. Maybe I need to review
git commands again <sigh>. Would this mean that my current git pull of
Orca dies not include 3.14 changes?

On Fri, Oct 24, 2014 at 07:09:23AM +0200, Peter V?gner wrote:
Hello,
What is so confusing to Steve about this is that arch linux AUR package of
orca uses git describe for retrieving its version string. Since git describe
puts latest tag in its description it is now version 3.13.91 or something
verry similar. We had a discussion on this about a week ago on one of these
lists either orca-list or sonar gnu linux support list.
The curent git master produces a version of orca which when instructed to do
so prints its version string as 3.15.something. There has been no tagget
3.15.x release yet it's why AUR PKGBUILD script confuses you all like hell.


Greetings

Peter


On 24.10.2014 at 03:53 Luke Yelavich wrote:
On Thu, Oct 23, 2014 at 09:04:24PM EDT, Steve Holmes wrote:
I just pulled the latest git version from Master and I still see
3.13.99 in the version of Orca. When I list branches in git with "git
branch -l", it just shows Master. Should there be a later version of
Orca out there?
Git master of orca for me has the version at 3.15.1pre. have you updated your local master branch copy?

As for branches, there is origin/gnome-3-14 which you can get a local checkout of and build. There are 
also tags for the releases.

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
_______________________________________________
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


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]