On Thu, Mar 29, 2012 at 2:46 PM, Ken Dreyer <ktdreyer(a)ktdreyer.com> wrote:
2012/3/29 Sérgio Basto <sergio(a)serjux.com>:
> On Thu, 2012-03-29 at 12:45 -0600, Ken Dreyer wrote:
>> 2012/3/29 Sérgio Basto <sergio(a)serjux.com>:
>> > Hi,
>> > other question about kmod , when I install VirtualBox-OSE , shouldn't
>> > Requires: kmod-VirtualBox-OSE ?
>>
>> On PAE kernels, this would unnecessarily require the non-PAE kernel
>> and non-PAE kmod.
>
> We already don't have PAE kernels ..
PAE kernels are still around. Check out a recent kernel build:
http://koji.fedoraproject.org/koji/buildinfo?buildID=307992
Or check out VirtualBox's kmod packages themselves:
http://download1.rpmfusion.org/free/fedora/updates/16/i386/repoview/kmod-...
vs.
http://download1.rpmfusion.org/free/fedora/updates/16/i386/repoview/kmod-...
It's probably best just to tell your users to download the correct one manually.
I wonder if there's a way to do a more generic Requires using rpm
metadata and not a specific package name. I tried repoquery to see the
difference between the PAE and non-PAE package but I got confusing
results:
# repoquery --provides kmod-VirtualBox-OSE
VirtualBox-OSE-kmod = 4.1.10-1.fc16.1
kmod-VirtualBox-OSE = 4.1.10-1.fc16.1
kmod-VirtualBox-OSE(x86-64) = 4.1.10-1.fc16.1
kmod-VirtualBox-OSE-PAE = 4.1.10-1.fc16.1
kmod-VirtualBox-OSE-smp = 4.1.10-1.fc16.1
kmod-VirtualBox-OSE-xen = 4.1.10-1.fc16.1
# repoquery --provides kmod-VirtualBox-OSE-PAE
(no output)
That seems strange to me.
Richard