You only need to switch to current each time you make a modification
to the spec that improves the module for a given kernel.
Buildforcurrent implies that an akmod-foo package will be built.
I take care of the switch for newest when a new kernel arise, so you
don't need to take care of this. But just remind to switch back to
current when you make an improvement.
Usually we push version changes when a new kernel hits stable updates
in fedora, so users are already advertised to reboot.
This is usefull, specially when there is a hard dependency between the
userland application and the kernel module (broadcom isn't concerned
Does that answear your question?
Yes, the process is clearer now!
Please build the wl-kmod and broadcom-wl packages only in devel for
now because we are still in the middle of the branching for F-16. (you
can cvs-import for both devel and F-16, but only build from the devel
Ok! I'll try to setup my environment as soon as possible to do so.
As all users don't switch to a new Fedora release when it becomes
available (wait for more stability or driver port for example), will it
be possible to "backport" later these packages for F-15 (when builds for
devel succeed for example)?