On Wed, 2005-03-30 at 10:40, Ping Yeh wrote:

> > CASTOR-client, e.g.
> > http://linuxsoft.cern.ch/cern/slc304/updates/i386/RPMS/CASTOR-client-1.7.1.5-1.longname.i386.rpm
> > 
> > Regards
> > Jan
> 
> Thanks for the pointer.
> 
> Is there any plan to put these CERN-related RPMs into a self-consistent
> yum or apt repository?

We have for CERN=SLC3, i.e. not the "main" SL release:
  rpm http://linuxsoft.cern.ch  cern/slc30X/i386/apt  os updates

(see http://linux.web.cern.ch/linux/updates/)
I think CERNLIB is also somewhere on contrib for SL3 (which has yum
headers), and perhaps the current CASTOR-client RPM could be added there
(but there is indeed the issue of rfiod starting by default)


>   If the CERNLIB RPM had a
> 	Requires: CASTOR-client
> line in the spec file at building time it would work seamlessly.

I guess figuring out the required package to satisfy that dependency
would be apt or yum's task. The upcoming change in CASTOR packaging is a
good example why we don't want to hardcode the package name in the
.spec.


> Another issue is that one has to properly define $CERN, $CERN_LEVEL and
> $PATH after installing the RPM to get the package working.  Can these be
> done by providing a /etc/profile.d/cern.{sh,csh} in the RPM?

Could be (fairly trivial), but I think the current reasoning goes like
* CERNLIB has been declared to be obsolete and is to be replaced by
Geant4
* only "legacy" users should be using it
* these "legacy" users will have their environment already configured
(including the experiment-specific desired version) , e.g via the HEPiX
scripts
 
Regards
Jan