VSSP packages: Procedure to Install

This note explains the procedure for public installation of your fine package in the VSSP group. It assumes that all the guidelines have been followed.
  1. Make a tar file, e.g. Xmgf.tar.
  2. Email Phil, saying where he can find the tar file, and what version number it is.
  3. Phil will make /vol/vssp/src/Xmgf containing owner=root /vol/vssp/src/Xmgf/Xmgf_1.0.tar.Z - backup tar owner=root /vol/vssp/src/Xmgf/Xmgf_1.0 - last major release owner=author /vol/vssp/src/Xmgf/Xmgf - current release owner=author /vol/vssp/src/Xmgf/Xmgf.tar - current release tar The last major release will be a stable copy kept in reserve for accidents eg. when a recent bug fix causes the package to crash while the author is away. Since the author owns the current release, bug fixes and enhancements can be implemented immediately without supervisor assistance.
  4. Phil will check that Xmgf_1.0 builds OK.
  5. Phil will now create 3 distinct author-owned directories all called /vol/vssp/packages/local/Xmgf but automounted according to the architecture. These directories will all contain a subset of /bin /lib /man /inc and any other directories specified in your README, e.g. bitmaps.
  6. The author now goes to directory cd /vol/vssp/src/Xmgf/Xmgf/src and builds his package using vssp-build 'one_line_make_command' This script does an rsh to each architecture and optionally copies the files to the local directories. All the local copies are immediately copied over unless the -r option is set.
  7. Phil will create soft links from /vol/vssp/packages/bin/Xmgf -> /vol/vssp/packages/local/Xmgf/bin/Xmgf and likewise for the 2 other architectures, and /inc /lib /man and any other soft links you may need as described in your README.
  8. If you did not make the local copies when building then the package libraries/binaries/includes/man pages will all track over to /vol/vssp/packages/local/Xmgf directories overnite.
  9. Send a short 5 line paragraph in ascii/html on your package to the hypertext manager (Majid) for inclusion in the VSSP packages directory, and post a message to the news board.

Updating the package

A significant benefit of this system is that the author may fix bugs and make minor enhancements without requiring assistance from the system manager. The system will be efficent if authors take care to test changes thoroughly before updating the public version. Updates are made as follows:
  1. Modify the files in /vol/vssp/src/Xmgf as necessary. Probably by untaring the latest version from your home directory.
  2. Either
  3. Post to the news board if your changes may affect users.

A.Stoddart@ee.surrey.ac.uk
August 1994