On Mon, Dec 14, 2009 at 4:55 PM, Robert G. Brown <rgb@xxxxxxxxxxxx> wrote:
Hi y'all,
A question. I upgraded by laptop to F12, which went fine, and then
proceeded to "dress" it by adding on a handful of non-repo RPMs as I'm
guessing many people do. This particular time I added e.g. the
VirtualBox rpms, as I wanted to experiment with alternatives to non-open
VMware.
Sun provides an F12 RPM (not in a repo, of course, grrr) so I grabbed it
and proceeded to try a straight rpm -Uvh install. Naturally it had a
string of a dozen dependencies in its dependency tree, and I found
myself right back in RPM hell, helped a little bit by yum (I could do
yum provides to find rpms that filled in the missing pieces easily
enough, and then do a yum -y install) but RPM hell nontheless.
Which leads me to my query. I'm guessing that this isn't an uncommon
situation -- a homebuilt RPM or RPM provided by a third party that won't
just "install" because it isn't in a repo, even when all of its
dependencies ARE in connected repos. Can yum do that? e.g. is there a
mode or add-on that lets one:
yum install VirtualBox-whatever.rpm
so that yum creates a dependency list from the rpm itself and then does
its yum-thing and looks in its repos for a list of rpms to resolve the
recursive dependency tree, then installs the whole thing for you?
rgb
If you don't need USB support in VirtualBox then you can just type
yum install kmod-VirtualBox-OSE-PAE
to install the open source edition of VirtualBox (You need to have the rpmfusion repos enabled)
Then you dont have to mess with compiling your own kernel modules etc.
Tim
_______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
