On Thu, Mar 29, 2012 at 2:00 PM, Richard Shaw <hobbes1069 at gmail.com> wrote:
> # repoquery --archlist=i386,i686 --provides kmod-VirtualBox-OSE-PAE
> VirtualBox-OSE-kmod = 4.1.8-1.fc16.16
> kmod-VirtualBox-OSE-PAE = 4.1.8-1.fc16.16
> kmod-VirtualBox-OSE-PAE(x86-32) = 4.1.8-1.fc16.16
>
> Why would the non-PAE package provide a PAE name?
It has to satisfy this line in the userspace VirtualBox-OSE.spec
93 Requires: %{name}-kmod = %{version}%{?prereltag}
kmod-foo is the actual kmod, versus
foo-kmod is a virtual "provides" to satisfy dependencies. Each kmod
varient provides it.
http://rpmfusion.org/Packaging/KernelModules/Kmods2#kmodtool
Kmods make me cross-eyed sometimes :)
But in Sergio's case, when I install VirtualBox-OSE, it already pulls
in the appropriate kmod- package:
yum install VirtualBox-OSE
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package VirtualBox-OSE.i686 0:4.1.8-1.fc15 will be installed
--> Processing Dependency: VirtualBox-OSE-kmod = 4.1.8 for package:
VirtualBox-OSE-4.1.8-1.fc15.i686
--> Processing Dependency: libgsoap++.so.0 for package:
VirtualBox-OSE-4.1.8-1.fc15.i686
--> Running transaction check
---> Package gsoap.i686 0:2.7.17-4.fc15 will be installed
---> Package kmod-VirtualBox-OSE-2.6.42.12-1.fc15.i686.PAE.i686
0:4.1.8-1.fc15.10 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
VirtualBox-OSE i686 4.1.8-1.fc15 rpmfusion-free-updates 18 M
Installing for dependencies:
gsoap i686 2.7.17-4.fc15 updates 198 k
kmod-VirtualBox-OSE-2.6.42.12-1.fc15.i686.PAE
i686 4.1.8-1.fc15.10 rpmfusion-free-updates 164 k
Transaction Summary
================================================================================
Install 3 Package(s)
Total download size: 19 M
Installed size: 68 M
Is this ok [y/N]:
- Ken