Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1556

News	FAQ
Search	Home

Subsections

• The penultimate build
• Creating the ISO and CD images

Preparing the binary

The penultimate build

Once the release build is in good shape we need to produce the files necessary for the binary distribution. Binrel must be run on each architecture. One should avoid binrel on nfs mounted disks as it takes considerably longer.

linux

1.

. /usr/local/aips++/aipsinit.sh

2.

binrel -tgt /home/cluster2/aips++/binary_release

3.

cp linux.tar.gz /home/tarzan5/aips++/binary_release

solaris

1.

. /usr/local/aips++/aipsinit.sh

2.

binrel -tgt /home/tarzan5/aips++/binary_release

Creating the ISO and CD images

Typically we burn on the aips2 administrator's computer. This involves copying the source contents from the binrel/YY.XXX directory to the CD distribution directory. The current content for v1.7 are listed below. Note the INSTALL, README, and VERSION files need to be adjusted for each release.

[wyoung@crestone cds]$ ls -1 cd1/*
cd1/data.tar.gz
cd1/docs.tar.gz
cd1/INSTALL
cd1/lib.tar.gz
cd1/linux.tar.gz
cd1/README
cd1/startup.tar.gz
cd1/sun4sol.tar.gz
cd1/VERSION

cd1/source:
admin.tar.gz
aips.tar.gz
atnf.tar.gz
bima.tar.gz
contrib.tar.gz
dish.tar.gz
display.tar.gz
doc.tar.gz
hia.tar.gz
install.tar.gz
jive.tar.gz
nfra.tar.gz
npoi.tar.gz
nral.tar.gz
nrao.tar.gz
synthesis.tar.gz
tifr.tar.gz
trialdisplay.tar.gz
trial.tar.gz
vlbi.tar.gz

Once the release has been assembled in the proper directory, xcdroast is used to create both the ISO image and burn the CD. Note: the ISO/CD image should always be labeled aips2install. Xcdroast usually creates a file track-01.img as the name for the ISO image, rename it to something more sensible, i.e. aips2vXY.iso.

The ISO image maybe tested using the loopback file system

mount aips2vXY.iso /mnt/iso -o loop=/dev/loop3,blocksize=1024

Now test install and verify both the ISO and CD images.