GNOME.org
 

Re: [orca-list] What is latest Orca/arch orca-git question

Yes, this does help. I did checkout commands with git, was just stumped with the lack of 3.15 showing up on 
the downloads page. I should have run orca 
-v to check while I'd still had the orca-git package installled, as I did suspect something similar to what 
you have explained. Your kind help has put 
things in to much better focus for me/thanks much. 
The bottom line is I spent some time confusing myself when I was indeed up to date all along, but out of that 
confusion, mostly thanks to your 
assistance I now have a clue...smiles.
--
Burt


On Mon, Oct 06, 2014 at 11:34:00AM +0200, Peter V?gner wrote:

Hello,
Okay I'll try again and hopefully I won't forget something.
Downloads from the gnome site are tagged commits from gnome git repository.
So if you know how you can get the same version from git like you would from
the gnome ftp site.
in your branched tree you can for example do
git checkout ORCA_3_13_92
you can list all the tags by simply typing
git tag | more
If you will not check out a particular branch or a specific tag you are
building so called head revision from the master branch.
If you have checked out a branch or a tag you can go back to master by
calling
git checkout master
What orca-git AUR package PKGBUILD script does is that it branches an orca
git repository on the first run. On subsequent runs it only pulls new
commits. Then it mirrors it locally and uses normal
./configure & make & make install
so if you  branch orca git repository and either compile it manually or
using orca-git package you will receive the same orca installation.
However due to the fact there is no tag corresponding with orca 3.15 pre
version in the orca repository, orca-git AUR package has nothing to base its
version string on and it uses latest available tag.
After installing resulting package you will get the following output
$ orca -v
3.15.1pre
$ pacman -Qi orca-git | grep Ver
Version         : 3.13.90.r127.g8ce18bd-1
This is all just cosmetic as you can see because there was not much
development for orca 3.15. However hopefully now you might be able to get
the idea.

Greetings

Peter

On 06.10.2014 at 04:51 B. Henry wrote:

Peter, I saw that on the download page, but why then when I did a normal git clone I have a version called 
3.15.0-pre and when I build the orca-git
package I get 3.13.90.r.127something or another, and on the d-load page I see 3.13.92 as the most recent 
alternative to 3.14?
Is 3.15 just renamed 3.13.90.r.latest, and is that the same as 3.13.92, or???
Sorry for being such a pain, but this is not the kind of behavior that one would ideally have  in some way 
or another...smiles.
And, thank you again for taking the time to talk about this.


On Sun, Oct 05, 2014 at 08:15:08PM +0200, Peter V?gner wrote:

Hello,
There were no commits made to the orca master branch during last week and a
few days.
For you reference this is the latest commit:
commit 8ce18bd0ff2d906f1f322c51e23b2c40a8ce92a6
Author: Kalev Lember <kalevlember gmail com>
Date:   Fri Sep 26 17:13:26 2014 +0200

    Fix desktop file keywords in Slovenian translation

    It's a string list and must be terminated with a semicolon.

So again I suspect all is good and whatever you are using to rebuild the
orca-git package is fine. Either you are manually calling
makeps -s
or using packar yaurd or whatewer then you should get the result.

Greetings

Peter

On 05.10.2014 o 16:23 B. Henry wrote:

This was helpful, but there's a problem as I mentioned, orca-git does not install latest at this point.
I do not know how long exactly 3.15 has been available, but I'm still getting the same build as I did 
from close to two weeks ago/tried maybe 4
times/and as I said, it's pretty slow to build here.
Your suggestion sounds good, will test here along with another idea.
This happened before when 3.13 was fairly new. Maybe there were not many changes commited, but it 
appeared that the package did not update when it
should have according to list mail indicating that some changes had been comomitted.
Thanks again,
--
B.H.



On Sun, Oct 05, 2014 at 12:30:31PM +0200, Peter V?gner wrote:

Hello,
I'llattempt to give some answers.
- At this point no update to orca-git package in aur is required. No
dependencies have been added removed nor any other dependent arch packages
have changed.
- What PKGBUILD script from orca-git packages is that pulls from orca git
master and compiles it each time from scratch. It calls
git describe --tags
for retrieving orca version.
So although orca is currently at version 3.15 it has not been tagged in the
git repository like so it's why arch package version does not match. I think
this is just a minor issue and as I have already suggested before, it would
be nice to change arch package version scheme rather than relying on git
tags being preciselly in sync with orca versioning.
E.G. by calling the following inside cloned orca git repo you will get a
nice version string that increments by one with each new commit
echo $(git rev-list --count HEAD)+g$(git rev-parse --short HEAD)
This is what other aur packages pulling from git tend to use as it it
requires no extra steps from the software maintainers.
Orca build system touches files in order to be able to figure out which
translations have been updated since you have performed last build. Since
orca-git package PKGBUILD script builds everything from scratch it takes
slightly longer to complete.

Greetings

Peter

On 05.10.2014 at 08:33 B. Henry wrote:

I have been using the orca-git package to update from master for a while now, and have not seen an 
update since orca-git-3.13.90.r127.g8ce18bd-1
First question is does the maintainer need to update something when the first numbers change, e.g. 
3.13.90?
As I've not seen an update for some time I went to the downloads page and saw 3.13.92 and 3.14. Of 
course I'm well aware that 3.14 has been around for a
while now, but  I saw mentioned 3.15 pre mentioned on the list with in the last day or so.
So I clone from git and see that it is indeed 3.15pre.
What is the criteria for putting an odd numbered package in to tarballs and zip packages?
And another arch specific question:
It takes a good bit of forever to do all the touching and such for the various languages when 
installing the orca-git package, but it was fast wen I
manually built the package from the git sources. Why is this? Does something in the package managment 
system give this a low priority? I can't say it
mattered much whether I had a bit going on or not at the same time as I was installing the orca-git 
package, and I generally shy away from heavy
multitasking anyway, especially if I see my CPu's being pushed or memory's low.
Thanks in advance for filling in any of my blanks when it comes to understanding orcaversions and arch 
git packages.
--
B.H.





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