Package delivery

Registering as a developer

SAS packages are digitally signed by the upload utility `uploadsas'. Before you can start delivering packages, you must first register yourself with the SOC and provide your PGP public key which is used to authenticate your deliveries.

Delivering a package

To deliver a development version of your package please do the following:

Do 'make clobber' in the top level directory of your package.
Verify the following:

all the checks in the checklist are ok
make check gives only +, no -
make dist succeeds

Upload the package with the utility `uploadsas' which is available from the SOC

Notes

Before you can deliver a package you have to send a PGP user ID and public key to saslib@astro.estec.esa.nl. A public key is generated with pgp -kg.
New and updated packages for which a task description has been approved can be delivered at any time, without approval of the I&T teams, and will be incorporated into the development releases.
Only after the official I&T teams have approved the packages will they become part of an official release.
When the latest version of a package doesn't work with the latest SAS infrastructure, the package is removed from the development release until a working version is delivered.
The SOC will not systematically check that the delivered packages comply with (3) but only sample some of the deliveries.
The SOC will raise SPRs on problems encountered with a package.

Patches

In case a minor change will fix a broken package the SOC might decide to generate a patch.

A patch is generated with the following sequence of commands:

tar xfz package-major.minor.tgz
cp -ar package package.org
edit the contents of package and run make check
make -C package clobber
diff -r -p -N package.org package > package-major.minor.patch.patch

The generated patch is delivered the same way as a package. When it is accepted it will be distributed to the developers together with the normal packages.

Updated on: August 9, 2000