GARNOME IS NOW MAINTAINED IN SVN.Index | <-Prev | Next->
Fedora: yum install tla
Debian: apt-get install tla
Note: This howto requires tla-1.2 or newer.
To get a list of all commands.
To get more info about a specific command.
|tla command -H|
You can optionally create default checking rules. This is a good idea if you don't want to create checking rules on a per archive basis. This will be used by all archives that require gpg checking and that don't have a per archive checking rules file.
Make a dir called signing and create a file in it for signature checking. (Please make sure that you have gnupg installed)
|mkdir -p ~/.arch-params/signing|
Create a file called ~/.arch-params/signing/=default.check with the gpg checking rule in it.
|echo "gpg --verify-files -" > ~/.arch-params/signing/=default.check|
Let's create our checking rules on a per archive basis. Since we want rules that are specific for our archive and don't necessarily want to force all of our other archives (if you happen to have other archives) to use these rules we'll create a separate checking rules file. (Please make sure that you have gnupg installed)
If you haven't done so already, create the signing directory.
|mkdir -p ~/.arch-params/signing|
Create a file called ~/.firstname.lastname@example.org with the gpg checking rule in it.
|echo "gpg --verify-files -" > ~/.email@example.com|
We now need to grab Paul's GPG public key by running the command.
|gpg --keyserver pgp.mit.edu --recv-keys 36ED0708|
Now register the archive project name and location where GARNOME resides.
|tla register-archive http://cipherfunk.org/arch|
Let's check to see if the archive was registered. This should output the archive project name and location.
To see what branches/versions are available for GARNOME from this archive.
|tla abrowse firstname.lastname@example.org/garnome|
Okay, now we're ready to grab the latest version of the GARNOME archive.
|tla get email@example.com/garnome--stable garnome--stable|
Now just copy gar.conf.mk.in and gar.gnome.mk.in to gar.conf.mk and gar.gnome.mk respectively.
cp gar.conf.mk.in gar.conf.mk; cp gar.gnome.mk.in gar.gnome.mk
Now just cd into the desktop/ dir and start GARNOME.
So now that we have the GARNOME archive how do we update it?
Once we've updated our tree we can build the new packages.
cd garnome--stable/platform; make install
cd garnome--stable/desktop; make install
Note: You should also run a make install in whatever garball directory that you've built that is not included in desktop/ or platform/ if necessary.
To see a log of the changes that have occurred.
|tla logs -sD|
To see a list of the changes in a specific patch. For i.e. to see changes in patch-27.
|tla cat-log patch-27|
To see a detailed output of the changes via diff that have occurred since a particular patch.
|tla changes -q --diffs firstname.lastname@example.org/garnome--stable--0.1--patch-31|
If the output is too long, you can pipe it into a file to view later.
|tla changes -q --diffs email@example.com/garnome--stable--0.1--patch-31 > changes-patch-31-2004-03-18|
So what happens when there is a new branch version release?
Check to see what branch version you're currently using.
Check to see if a new branch version is available.
Make sure that the current tree is up-to-date.
Join the new branch.
|tla join-branch firstname.lastname@example.org/garnome--stable--0.1|
Set the version of your current tree to the new branch.
|tla set-tree-version email@example.com/garnome--stable--0.1|