Well re caveat.... I know what you mean and I have done the same.... I use SuSE...and have built things from sources and RPMS on different occasions and everything is functional with no major problems. I guess I was mostly just trying to say 'when in doubt keep it simple' and don't mix and match if you can avoid it cause I think it CAN create problems by accident 'if you don't know what you're doing'. Since RPMS are so 'smart' and know their own dependencies etc. it seems better if you can find all the RPMS to just use them. He was having problems so to me it seemed to make more sense to K*I*S*S* by keeping things simple and using a uniform installation flavor. My mistake I guess was I didn't think the RPM -Uvh or install options would detect libraries not installed by RPM because I thought it would only work with things in the onboard RPM database (though if you did build you could overide any refusals if you're sure you have the right stuff on board. But if you are mistaken --have wrong version #'s etc then it prob won't work right. )and I'm glad you corrected me as it prevents this mistatement from accidentaly being accepted as true and repeated by someone who doesn't know. I still think, though if someone is new to a system simplicity serves them well. And the best way to preserve simplicity and to prevent exasperation is to use uniform procedures if you are able. Anyways...all's well that ends well. Sorry Jules for snapping. Jules Bean wrote: > --On Thu, Jun 4, 1998 9:52 am -0400 Frag-A-Muffin > <[EMAIL PROTECTED]> wrote: > > > > > I don't know how true this statement is (the mix and match statement) cuz > > my system consists of tar.gz's and RPMs of libs and all my E stuff > > compiled and works fine. > > How true? > > It's complete rubbish. > > I couldn't be bothered to reply at the time, but I saw and realised that.. > > You can certainly mix and match RPMs and self-installed stuff. > > There are, of course, some caveats. But the caveats mainly apply in you > have RPMed and local versions *of the same library*. In this case, you > should decide which one you want, and remove the other - unless they're > different major version numbers, and you know what you're doing. > > In general, use RPM (or dpkg, if you're on debian like me) whenever you can. > If you need to try something that has not yet been rpm'ed or deb'ed, then > install it yourself, but make sure it goes into /usr/local. > > Then, when the RPM comes out, I recommend you install the RPM and remove > your hand done version - certainly, if an RPM of a newer version comes out. > > To remove a hand done version, you may be able to go into the source > directory and type make uninstall. I'm pretty sure this works for rasters > libs (kudos raster!). If this doesn't work, then go into /usr/local/lib and > manually rm the library files. > > In general, try to keep /usr/local/lib trimmed down to just those libraries > you've conciously installed by hand. You should be able to ls > /usr/local/lib and think "Yup, that's fine, I installed X because I needed > Y...". > > Jules - To unsubscribe from this list send mail to: [EMAIL PROTECTED] with the message contents: unsubscribe e-develop
