CVS

From LinuxHam
Revision as of 16:37, 1 December 2011 by DL5RB (talk | contribs) (Style cleanup - move interlanguage link to the bottom of the page.)
Jump to navigationJump to search

Anonymous CVS

For those who always want to stay on the bleeding edge, and want to avoid having to download patch files or full tarballs, we also have an anonymous CVS server. There are currently three amateur radio relevant modules in CVS archive, libax25, ax25-apps and ax25-tools.

cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs login
(Only needed the first time you use anonymous CVS, the password is "cvs")
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs co <module>

Web CVS

Browse the changes

Via cvsweb, you have direct access to the new AX.25 sources. The intuitive interface allows you to follow the development at the click of your mouse.

Download as tar archive

Automatically generated on the fly as you download these tarballs are always the very latest - with all the risk and benefits of living on the bleeding edge. Building requires recent versions of automake and autoconf.

libax25 ax25-apps ax25-tools

Latest releases

The best choice for the OM who just wants to keep his system going along happily. Unlike the raw CVS snapshots above these tarballs don't require any messing with GNU autoconf and automake.

ax25-apps-0.0.8-rc5.tar.gz ax25-tools-0.0.10-rc5.tar.gz libax25-0.0.12-rc5.tar.gz

CVS copy via Rsync

The CVS repository can also be fetched using rsync like this:

rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/<module> /local/directory
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/CVSROOT /local/directory

You can then check it out using:

cvs -d/local/directory co <module>

Quarterly snapshots

We plan to automaticaly generate snapshots quarterly, downloadable as tar archives.

Compilation notes

Build dependencies

install autoconf automake1.9 libtool libncurses-dev

Automake1.4 on debian sarge and etch is known to be incompatible in preconfigureing the hdlcutil FL-Widgets tree.

Bootstrap (autoreconf, make)

for dir in libax25 ax25-apps ax25-tools; do
  cd $dir && autoreconf --install --force && \
    ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man && \
    make && make install && cd ..
done

On a new fresh installation, you should do "make installconf" in the libax25 ax25-apps ax25-tools directories, too. But be aware, that make installconf overwrites existing configuration files in /etc/ax25/.

Note: earlier versions had a bootstrap script (with aclocal, autoconf and an appropriate ./configure line) but these days autoreconf should be used.

Naming conflicts

ax25-apps installs two program named call and listen. Despite ax25-apps using these names for longer than other packages various Linux distributions including Debian and Fedora have elected to rename these binaries. When building ax25-apps you want to make sure there are no such conflicts. Standard GNU autoconf which is being used by ax25-apps for configuration supports such renaming through the powerful but obscure --program-transform-name option like this:

./configure --program-transform-name='s@call@axscall@;s@listen@axlisten@' --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man

This will install the call program and its man page as axcall and listen as axlisten. The argument of --program-transform-name is a sed(1) program; adjust as need for your installation. Because this is a standard feature of GNU autoconf, all versions of ax25-apps and also ax25-tools support this.

64-bit systems

Most 64-bit systems are setup such that libs go to /lib64 /usr/lib64, /usr/local/lib64. Autoconf won't notice this; it will default libdir to <prefix>/lib. This means installation will overwrite whatever is there possibly damaging 32-bit compat versions of the libraries installed there. To get autoconf to do the right thing in this case you must pass --libdir=<prefix>/lib64 when configuring.

Maintainers

Maintainers for ax25-apps, ax25-tools and libax25 are

Please feel free to contact us in case of problems, bugs or fixes, patches, enhancements, feature requests, or just for your personal success story.