http://bugzilla.rpmfusion.org/show_bug.cgi?id=1999
--- Comment #8 from NVieville <nicolas.vieville(a)univ-valenciennes.fr> 2011-10-28
15:11:36 ---
(In reply to comment #5)
[...]
> One more question, the spec file contains actually this directive
>
> %define buildforkernels newest
>
> But to build the akmod-wl package this one must be set to:
>
> %define buildforkernels current
>
> How do I should set it to meet the akmods rpmfusion standards as this
> package provides a new version of the Broadcom drivers?
I don't know that, i'm not a akmod/kmod expert, try asking on the mailing list
maybe look in other akmod in rpmfusion.
After reading:
-
http://rpmfusion.org/Packaging/KernelModules/Akmods
-
http://rpmfusion.org/Packaging/KernelModules/Kmods1
-
http://rpmfusion.org/Packaging/KernelModules/Kmods2
I've modified the "buildforkernels" macros section of the spec file to:
#define buildforkernels newest
%define buildforkernels current
#define buildforkernels akmods
To be sure the new akmod package will be build for the current kernel. Once the
akmod package built, if I correctly understood the documentation, I have to
revert it to:
%define buildforkernels newest
#define buildforkernels current
#define buildforkernels akmods
This have to be kept until the next new upstream release of the wl-kmod needs
an akmod package to be built.
Thanks for commenting this if I've misunderstood the documentation. I'll ask to
the list too.
New spec file and srpms file provided:
SPEC:
http://dl.dropbox.com/u/25699833/rpmfusion/wl-kmod/wl-kmod.spec
SRPMS:
http://dl.dropbox.com/u/25699833/rpmfusion/wl-kmod/wl-kmod-5.100.82.38-1....
rpmlint as usual. I can provide rpmlint outputs if needed.
--
Configure bugmail:
http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.