Software Packaging
Table of contents
Overview
There are many software packages required to be installed on multiple sites of the LSC data grid. This section address issues on how to prepare, integrate, test, maintain, and release these software packages so that users are provided with easy and standard ways to update and install them with little bothers.
YUM
The rpm is used to pack each software. Corresponding software developers are responsible to provide these rpms (hopefully, we will try our best to be help on this of course).
Every rpm has a header. That header contains a complete file list, package descriptions, lists of what features/libs it provides, lists of what it requires, what it conflicts with etc. What Yum does is to copy the header from the rpms on the server (called a repository, just an HTTP or ftp server), then the client part of yum uses those headers to determine what needs to be installed/upgraded/erased.
Please go to here for more information on YUM.
List of Software
Totally four repositories (HTTP servers) will be maintained:
- FC2
- RH9.0
- FC3
- RHEL
- DMT
- fftw3
- gsl
- Glue
- libframe
- libmetaio
- LAL
- LALApps
- LDR
- MatApps
- ROOT
Contributors
- Patrick Brady
- Duncan Brown
- Junwei Cao
- Jolien Creighton
- John McNabb