|
Hi, Kyle,
Definitely not a silly question. To start off with,
if you want to stay up to date with the Orca branch, you should update your
version of Orca at least every time Will Walker sends out a message to this list
announcing a new version of that branch (that is, 2.24.x). That is a
minimum. However, if you want to get the new features sooner, then you can
update more often, such as every week or two. On the other hand, I don't know
how often updates to the 2.24 branch will occur in the future, given that 2.26
has just been released. I don't believe that they make many, if any,
changes to a branch once they have released a newer branch. I'm sure Will or
someone else on the development team will correct me if that statement is
incorrect.
As to the method you described, a lot of it is no
longer needed if you have built from a branch before. For instance, if you have
followed this process once before, you will not need to install gnome-common,
automake, or svn again. Also, once you have removed gnome-orca using apt-get,
you never need to do that again. As for the command:
sudo apt-get build-dep gnome-orca
you shouldn't need to do that one again unless you
have executed the following command:
sudo apt-get autoremove
It won't hurt to run any of these commands a second
time--the output will just tell you that everything is up-to-date or that
gnome-orca isn't installed.
If you have built a branch from svn before, all you
need to do is get into the directory where you downloaded the svn source
files (in your case, it looks like ~/downloads/orca, then do the
following:
svn up
./autogen.sh
make
sudo make install
The "svn up" command downloads any new files or changes to existing files from the svn
repository. If there are no updates to download, you'll get a message saying
something like "at revision 4641". If you get this message, you need go no
further. The other three commands build and install Orca.
Just for clarity, I should add one more
thing. If you had just continued using the gnome-orca package, you would
have gotten the branch updates eventually. It takes some time between the
release of a new version within the branch (those messages Will sends out) and
the updates getting into the repositories for your version of Linux. Ubuntu has
a reputation for doing this quickly, but I have no knowledge to back that
up.
Hope this helps,
dave
----- Original Message -----
|