Packaging and Distribution

External software

Who: Eric Poinsignon

How: Usually there is no request for a single external package but only on an AA project with its dependances. Now, one package can be distributed using this command:

cd /afs/cern.ch/sw/lcg/external;
tar zcvf distribution/< package >_< vesion >__LCG_< platform >.tar.gz < package >/< version >/< platform >/*

*When:* Only on requests.

Packaging and Distribution of the LCG software

Who: Eric Poinsignon

How: With Kuba's script: /afs/cern.ch/sw/lcg/external/distribution/lcg-installation-manager.py. The requested project plus all depending external software are distributed. The resulting files (tarfiles or rpms) are stored in /afs/cern.ch/sw/lcg/external/distribution

Example:
1- /afs/cern.ch/sw/lcg/external/distribution/lcg-installation-manager.py --project=SEAL_1_1_1 --arch=slc3_ia32_gcc323 list
2- /afs/cern.ch/sw/lcg/external/distribution/lcg-installation-manager.py --project=SEAL_1_1_1 --arch=slc3_ia32_gcc323 tar
3- /afs/cern.ch/sw/lcg/external/distribution/lcg-installation-manager.py --project=SEAL_1_1_1 --arch=slc3_ia32_gcc323 html

The web page : http://spi.cern.ch/lcgsoft/ is also updated, but separately.

When: At each release requested by the AA projects.

Packaging and Distribution of bug fixes/patches

For external software or LCG software

Who: Eric Poinsignon

How: As soon as an AA project releases, all dependances are frozen, therefore any bug or patch will need a new version name with _patch or _anyitem suffix that will live beside the used one.

When: On demand.

Update pacman cache (sources and binaries)

Who:

How:

When:

Prepare tarfiles for distribution (sources and binaries)

Who: cf : Packaging and Distribution of the LCG software

How:

When:

Help for non supported platforms

Who:

How:

When:

-- Main.aimar - 23 Nov 2004