Please report problems, suggestions to teuben@astro.umd.edu
Package Generic Name VID Size(Mb) ------- ------------ ------- -------- aastex aastex 502 0.44MB astromake astromake 0.93 0.03Mb dart dart 3.0.3 13.5Mb (*) ds9 ds9 2.1b4 5.3Mb gildas gildas mar01 128.5Mb jstatus jstatus hdf hdf 4.1r3 13.8Mb karma karma 1.6.33p 8.8Mb miriad miriad 01jun15 65.9Mb nemo nemo 3.0.5 20.1MB pgplot pgplot 5.2.2 1.6Mb saoimage saoimage 1.25 0.6Mb saord saord 1.8 20.3Mb sm sm 2.4 0.96Mb (*) xephem xephem 3.2.3 4.0Mb xgobi xgobi sep2000 7.6MB
(*) These packages must be obtained locally or from CD, since they have restricted distributions. See /apus/linux/astromake for a local copy.
cvs -d :pserver:guest@cvs.astro.umd.edu:/home/cvsroot login(use password: guest) after which the source code can be checked out:
cvs -d :pserver:guest@cvs.astro.umd.edu:/home/cvsroot co astromakeIt will create a directory astromake. The installation steps are as follows:
cd astromake ./configure make install source astromake_start (this defines $ASTROMAKE)after which added packages can start. Future updates to the astromake package should be done as follows:
cd $ASTROMAKE cvs update -d ./configure make install
wget ftp://ftp.astro.umd.edu/pub/astro/astromake_1.0.tar.gzand install it anywhere you like it (you don't have to be root)
% tar -zxf astromake_1.0.tar.gz(careful, some mailcap files will go install that tar file if you left-click on the URL from a thus-activated browser).
After this you should install astromake itself on your system:
% cd astromake_1.0 % ./configure % make install % source astromake_startNow you are ready to install/de-install packages. Note this assumes you have plenty of disk space. Sometimes this can be alleviated by placing proper symbolic link in either $ASTROMAKE/opt.
astromake all saoimage saordwould fetch the saoimage and saord packages from our site, install them and remove the temporary tar files. If for some reason you need an older version, or specific version, most packages are stored with a version id (VID) in their file name:
astromake -v 22feb99 all miriadIf, for some reason, you have copied the interesting files from the archives ( ftp://ftp.astro.umd.edu/pub/astro/), installation is done using the install directive:
astromake install miriadThis applies in particular to packages which we cannot legally put on our anonymous ftp server. You need to copy those packages from your CDROM version or /apus/linux/ or /apus/linux/astromake directory.
source /astromake/astromake_startafter which any package can be loaded using the 'astroload' alias:
astroload miriad ds9 nemoIf you need to load a specific version, for packages that support multiple versions, use the -v flag:
astroload -v 99sep12 miriadand to see which versions are supported by the packages on your version of astromake, use
astroload -vThere are normally under control of your astromake site administrator.
If you want to develop your own package under astromake, have a look at examples in /usr/local/astro/make/files on how to add a 'makefile'. Issues around how to get it working under the various linux distributions can still be problematic, not until LSB is adopted. See e.g. Linux Development Platform Specification V1.1.
Another approach to package your software is Xstow and GNU Stow.
See also the "Usepackage Environment Manager ", you can find a version on freshmeat, as well as SoftPKG
Yet another one is smart.
Now writing this in 2012: the more mature version that seems to be prevelant on many linux distributions is Environment Modules. In redhat based systems this package is called environment-modules.
This page was last modified on 17-Aug-2022 by teuben@astro.umd.edu.