begin quoting John Oliver as of Thu, Mar 22, 2007 at 01:16:45PM -0700: > On Thu, Mar 22, 2007 at 12:28:59PM -0700, Gregory K. Ruiz-Ade wrote: > > [snip] > > Why are you trying to install an older version than what's already > > installed, though?
C++ can be very version-dependent. To the point where symlinking a newer version of a C++ library to an older version (which should work with libraries) will crash applications. > The application being installed depends on the existence of libgcc, > compat-libstdc++, and zlib So, the installer was written to rpm -Uh > them, with the theory that if they're already there, great, and if > they're not, then they will be. So why not use ";" instead of &&. > The older version is almost certainly what comes with the base RHEL4, > whichever Update level they had to work with. > > Like I said, I considered updating the package with the newer libgcc, > but then I would also have to include the RPMs for every conceivable > package which might depend on libgcc, which I do not want to do. RPM won't let you have multiple versions of the same library? > Right now, my problem is that, in my elif case, when the RPM > installation for libgcc fails, it doesn't just go on to try to install > compat-libstdc++ and zlib... it appears to dump out of the elif case > entirely. I'm looking for a way for the script to handle this a little > more gracefully, hopefully without having to test for the existence and > version level of each RPM dependancy. There's a reason they call it "dependency hell"... -- Applications should ship the the libraries they require if they're going to be picky about what revision they'll work with. Stewart Stremler -- KPLUG-List@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
