On Thu, Mar 13, 2003 at 01:07:29AM +0100, Brian Reichholf wrote:
>
> strangely enough though after emergeing rpm and executing rpm -ihv
> <package>.rpm it tells me that i don't fulful the requirements (i
> manually checked.. and i *do* have all the .so's required - it doesn't
> ask for packages, just so's)
Yeah, RPM doesn't just keep track of the presence of particular packages
and their contents, but also certain key capabilities (I forget the term
they actually use) which are provided by packages. In some cases those
capabilities look strangely like files (as in your present case where
they're dynamic libraries), but RPM doesn't look at the filesystem, it
looks at its database of installed stuff.
Since none (or few) of your dependencies are installed via RPM, RPM
doesn't know anything about them and will think they're missing.
> any suggestions?
Given that you're living on a system that doesn't rely on RPM primarily
for package management, one possibility is to use the --force option,
effectively telling RPM to STFU and just install the damn package
already. But since you don't really care about RPM's package management
facilities -- you just want to copy this software onto your system --
I'd probably opt for a different approach. Convert the .rpm(s) to cpio
archives (rpm2cpio, IIRC); this will allow you to unpack them anywhere
(say, /usr/local/PACKAGENAME, or wherever) and avoid mucking up your
main / and /usr.
Of course, if they didn't compile their binaries to be relocatable you
can give yourself new problems when you try to run the software. In
that case the next thing I'd try would be to symlink the relevant files
into the places where they expected to be installed.
HTH,
-mrj
--
Michael Jinks, IB # Enterprise Networks & Systems Administration # UofC
Reader! Think not that
technical information
ought not be called speech; -- Anonymous, "How to decrypt a DVD"
--
[EMAIL PROTECTED] mailing list
