Package delivery

Registering as a developer

Delivering a package

1. Do 'make clobber' in the top level directory of your package.
2. Verify the following:
1. all the checks in the checklist are ok
2. make check gives only +, no -
3. make dist succeeds
3. 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

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