mrtg problems

[Jeremy Fowler]

However, you CAN have more than one copy of libpng, etc. on your system. The default install prefix 
is /usr/local/lib most RPMs install in /usr/lib. If you compile mrtg or any other package to use 
the libs in /usr/local/lib it doesn't effect the rpm versions that are installed in /usr/lib and 
all other RPM dependencies WILL remain intact. 

However, building your own updated RPM isn't all that difficult. Just download the source RPM for 
the current library you have, install it (which it will end up in /usr/src/redhat <might be 
different for caldera, dunno>), copy the latest tarball to /usr/src/redhat/SOURCE and then edit the 
spec file in /usr/src/redhat/SPEC to update the version numbers, then compile a new package with 
`rpm -bb <package>.spec`. You new rpm will be in /usr/src/redhat/RPMS/i386 (or your arch).

One gotcha you should lookout for is patches. There may be one or two system specific patches that 
customizes too your system, which is fine. Just remember to comment out patches that only apply to 
the older version of the package in the spec file before building.

> -----Original Message-----
> From: owner-kclug at marauder.illiana.net
> [mailto:owner-kclug at marauder.illiana.net]On Behalf Of Jason Clinton
> Sent: Tuesday, September 03, 2002 2:50 PM
> To: mike neuliep
> Cc: jfowler at westrope.com; kclug at kclug.org
> Subject: Re: mrtg problems
> 
> 
> mike neuliep wrote:
> 
> >Jason,
> >
> >    I'm doing this on a Caldera system.  It uses RPM and I am not totally 
> >familiar with RPMs and how Caldera manages (or redhat for that matter) how
> >they manage their packages.  However I am very familiar with Debian.  What is
> >redhat's or caldera's equivalent to debian's dselect program?  I'm 
> not running
> >X so I'm doing everything from bash shell.  Initially I installed the mrtg as
> >an rpm and it didn't complain about dependencies.  After that I did 
> the compile
> >like Jeremy Fowler suggested and then everything was hunky-dorry. 
> >
> >	Mike
> >  
> >
> The problem with installing from source on a package manages system is 
> if anything ever depends on any of the items you built from source (and 
> alot of things depend on libpng, zlib, and gd)  you're kinda up a creek 
> without a paddle unless you go back and install them all over again as 
> RPMs. I've not familiar with the method by which an RPM is created. I 
> once started to read about it and then quickly realized I hated RPMs. On 
> the other hand, all the packages you just installed from source should 
> be out there somewhere as RPMs already.
> 
> Once you have them, I suggest you run RPM like this to find out what the 
> dependicies are for any given package:
> 
> # rpm --requires foobar.rpm
> 
> At this point I don't believe Caldera has implemented anything like 
> APTGET or EMERGE to automatically fetch and install dependicies.
> 
>