[oclug] RPM dependancy prob
m.rosberg at telesat.ca
Wed Sep 7 10:51:11 EDT 2005
Thanks for all the input.
I completed the Cacti install from RPM using the --nodeps option. I had
to modify the PATH variables for RRDTool in the Cacti configuration.
This seems to be the only side affect from having installed RRDTool from
source code versus RPM.
PHP is another package that Cacti depends on. A past Cacti install that
I performed recommended that I upgrade PHP to a later version. That
upgrade caused a chain reaction that ended up with me upgrading another
10 or so packages that I hadn't planned on. Thus the caution with the
RRDTool install this time around.
> -----Original Message-----
> From: Vic Gedris [mailto:vic at gedris.org]
> Sent: Tuesday, September 06, 2005 10:49 PM
> To: General Membership Discussion List
> Subject: Re: [oclug] RPM dependancy prob
> On Tue, Sep 06, 2005 at 03:15:10PM -0400, Rosberg, Michael wrote:
> > Do RPM dependencies have to be installed by RPM? Is there
> any way that
> > I can make the Cacti package aware on my RRDTool install?
> > [root at dvbrcspop/download]# rpm -ivh cacti-0.8.6f.fc4.i386.rpm
> > error: Failed dependencies:
> > rrdtool is needed by cacti-0.8.6f-1.i386
> Another option that nobody mentioned is the "checkinstall"
> package. If compiling from source, you can do "checkinstall"
> instead of the "make install" step, and checkinstall will
> build a package of your choice.
> In my experience, checkinstall didn't always work, but it's a
> nice fast way to have RPMs/debs created for your system
> without having to manually make spec files, etc.
> Vic Gedris | Web: http://vic.gedris.org/
> Toronto, Ontario | E-mail: vic-at-gedris-dot-org
> CANADA | Encrypted email preferred (D77B43FB)
More information about the OCLUG