RE: setup of redhat RPM Postfix with Redhat RPM SASL


Subject: RE: setup of redhat RPM Postfix with Redhat RPM SASL
From: Dan Vande More (dvm at firstlink dot com)
Date: Tue Apr 15 2003 - 15:40:03 EDT


Sounds like your creating so many problems with RPM's you'd be better
off installing from source.
Ask around with experienced linux people, and I would assume most hate
rpms. Mainly because if you can get them to do what you want them to do,
you've spent 3 times as much time as you wanted to.

If you have fairly identical servers, simply do a ./configure <options>
make make install.

Then tar and gzip that dir, and do a make install on the remaining
servers.

Of course, this is a little different for sasl, I posted to the list
about 2 weeks ago how the only way I got sasl installed was by
installing an openbsd package.

Just my 2 cents.

-Dan

-----Original Message-----
From: Edward Rudd [mailto:eddie at omegaware dot com]
Sent: Tuesday, April 15, 2003 12:46 PM
To: Ken Murchison
Cc: Cyrus-SASL
Subject: Re: setup of redhat RPM Postfix with Redhat RPM SASL

yeah
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
package..
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>







Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD