On Wed, Apr 26, 2006 at 10:54:48AM +0100, Alessandra Forti wrote:
> >>I think the rpm should not override the .batch files it should create an
> >>rpmnew version.
> >>
> >
> >It is dCache view that the .batch files are part of the software and so
> >can be updated whenever a new version comes out. Probably a good idea to
> >backup your /opt/d-cache/config directory before performing an upgrade.
> >
> >
> I disagree and would like this to be inserted in the list of problems
> Owen will present them.
> To them it doesn't make any difference.
Here is what they say in the book:
If, prior to the upgrade, you changed anything in a batch file
(config/<domainName>.batch) these changes will be moved to files
with names config/<domainName>.batch.rpmsave. There have been
major changes to the batch files. Therefore it is necessary to
reapply your changes. However, keep in mind that the batch files
are considered to be part of the software and not configuration files.
It should not be necessary to change them in most situations. Try to
find a prober configuration variable in config/dCacheSetup. (See the
template in etc/dCacheSetup.template for hints.) If it should still
be necessary to change a batch file, contact <[log in to unmask]>
and report a ?request for enhancement?. (See Chapter 5, The Cell
Package for background information on the batch files.)
They do not consider the .batch files as configuration and they
usually do change a lot of things there so keeping the old one
might not work. We should be asking them to move the settings to
dCacheSetup.
> It is probably 1 line in the rpm configuration file.
True it's just %config(noreplace) file instead of %config file.
|