Part 3: xlog - Preparing to hack

The previously published parts of this series can be found here:

• Part 1: Logging Software for Amateur Radio contacts - xlog
• Part 2: Hacking on xlog
• Appendix: References/links

So, we've downloaded the source code for xlog from the CVS repoistory:

  cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/xlog co xlog

Even before configuring, the first thing I do is put the whole thing into a Git repository. The main reason for doing this upfront is that it then becomes possible to see what files are created or altered during the software building process. When we get around to making changes we can then make use of branches and commits.

  cd xlog
  git init-db
  git add .
  git commit -m 'Initial commit'

Use 'git status' to see which files are different.

Lets now build the software, as per README.cvs.

  ln -s ...
  autoconf
  automake
  ./configure
  make
  make install

Now, 'make install' will fail unless you give yourself system (root) privileges as it will try to install the code into the system directories (eg. /usr/bin, /usr/lib etc.). For the developer, there are several methods to get around this requirement. I use a tool called 'epkg', which allows software to be installed

To update the repository from upstream:

  (commit any outstanding changes to another branch)
  git checkout master
  cvs update

These changes can then be pulled into a local working branch by using:

  git checkout (your-branch)
  git rebase master