On Sun, 2003-06-15 at 07:40, stefmit wrote: ... > > > > no different than what is done with Apache... the compile-from-source > > package puts everything related to foobar in /usr/local/foobar because > > that's where it is expected. The came-with-the-OS package (or contrib in > > this case) puts all configuration in /etc, all logs in /var, all > > libraries in /usr/lib, etc. That's the way distros are. If you don't > > want to do it that way, then download the source from nagios.org and > > configure it, then make rpm. > > > Sure - wish you were right ... you probably missed the other part of the > email: I WANTED to use nagios from the source (i.e. 1.1), as it was fixed for > a couple of things. But the www part won't install ... guess why? Because of > some libraries problems, which ... and here I can start all over again with > my original email ... >
You were probably missing gd-devel -- there's some weirdness there with Mandrake's RPM-naming scheme (foobar1-0.3.i586.rpm vs. foobar-1.0.3.i586.rpm). > I guess the question still is: when you NEED a specific library, and "ln -s" > -ing with existing one won't work, WHAT are you doing? ... what are you doing? Installing from RPM or installing from source? If installing from source, having the binary library available as any name doesn't do you diddly, you have to have the headers from the -devel rpm. If installing from RPM and having dependencies problem, realize that the rpm tool doesn't look at your filesystem, it looks in its database. Hence the --nodeps I recommended earlier -- you've already made things so that they ought to work, so you need to override the old information in the rpm database. -- Jack Coates Monkeynoodle: A Scientific Venture... http://www.monkeynoodle.org/resume.html
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
