Accessing Arch

In order to access the GnuArch repository for the Developing with Gnome guide, you merely need to follow a few simple steps:

  tla my-id "Your Name <your@email.address>"
  tla register-archive http://www.gnome.org/~newren/arch
  mkdir ~/archives/local-repo
  tla make-archive some@randomString--anotherString ~/archives/local-repo
  tla tag -S -A some@randomString--anotherString \
    newren@gnome.org--developing-with-gnome/developing-with-gnome--main--1.0 \
    developing-with-gnome--mybranchname--1.0

If you've followed those steps, you have successfully made your own fork of my tutorial. Congratulations! To work on it, though, you first need to check out a working copy:

  tla get -A some@randomString--anotherString \
    developing-with-gnome--mybranchname--1.0 my-sandbox
  cd my-sandbox

You can now work and commit to your branch, get history, etc. without being connected to the network. This means: (1) you get local disk speed (i.e. operations are fast), (2) if my repository ever dies yours still works completely. Whenever you want to incoporate changes from my tutorial to yours, simply run (from your checked out version of your branch):

  tla star-merge newren@gnome.org--developing-with-gnome/developing-with-gnome--main--1.0
  tla log-for-merge >> some.log
  # Edit some.log and fix up the commit message
  tla commit -l some.log

To get your changes incorporated in the main version, you have to either generate a changeset (not suggested) or else publish your archive somewhere that I can obtain it so that I can run a star-merge from your archive to the main one. I will cover this later.

Note that this above outline is the exact same way I work with the archive. I could access it directly without branching, but I enjoy being able to work when disconnected from the network (or if the gnome.org servers go down...) and I like getting local disk speed.