[KLUG Members] rpm wierdness

[Adam Tauno Williams]

>>I have run into this many times before - especially when stalling
>>'out-of-my-distribution' RPMs (i.e. install mandrake, suse or
>>mirror-contrib rpm's on a redhat install, etc).  Don't quote me on this, 
>>but I think that rpm refers to its database rather than the actual 
>>presence of the file(s) it needs.
>>If for some reason it doesn't see an entry for libpq.so.2.0, it will
>>think it's not installed.  Simply override the dependencies (the second try)
>>with --nodeps once you have verified the file exists on your system.
>Ah, I see.... I had done the install with the --nodeps  option and it
>is working fine now. I had also verified that the file did in fact exist.
>OK, it was a symbolic link to a newer one <G>.

Usually that is just fine.  If you expereince erratic behaviour in the
application,  grab an src.rpm and rebuild.

>>The clean way to fix this in many cases is to get the .src.rpm and do
>>a:  --rebuild
>I'll keep this in mind for the next time!

I've taken to doing this almost be default for apps I really use alot,  you gain
some theoretical performance and stability (maybe 0.0000003%),  but it is just
soooo easy.

But does anyone know any simple way to pass in options to the build routine
(such as options to "configure")?  Currently I install, untarball, tweak,
re-pack the tarball, and then build the RPM.  Kindof a pain.

Systems and Network Administrator
Morrison Industries
1825 Monroe Ave NW.
Grand Rapids, MI. 49505