Subject: Re: setup of redhat RPM Postfix with Redhat RPM SASL
From: Edward Rudd (eddie at omegaware dot com)
Date: Tue Apr 15 2003 - 14:45:38 EDT
but there are consequences with --force that I don't like.
One as I am creating custom rpms for serveral servers I like to be able
to just do an "apt-get upgrade" on the machines and have them synced
with my setup..
Two, when "upgrading" to the same release file removal isn't done
correctly. At least not with RPM 4.0... For example
I create an RPM version 1.0-1 of some program install it.
then I accidentally put some files in the wrong place.. so I repackage
it with the files int he correct place and "Uvh --force" the new 1.0-1
all should be good right? but it isn't.
all of the files in the new package are there.. but so are all the files
from the old package that were in the wrong directory.. I've had this
happen on a number of occasions with RPMS.. so I now put a ".1" after it
for my "modifications" to official RPMS. Or I uninstall with --nodeps
and reinstall the fixed package..
On Tue, 2003-04-15 at 13:01, Ken Murchison wrote:
> Edward Rudd wrote:
> > 4) change the Release: tag toward the top of the spec to 5.1 (RH8) or
> > 11.1 (RH9) (so it'll be seen as "newer" than the stock RH rpms.
> This shouldn't be necessary if you use the --force option when
> installing the RPM. I do it all the time when I build my own custom
> kernel RPM and just blow over the existing one.
-- Edward Rudd <eddie at omegaware dot com>