Reindl Harald wrote:
> because akmods is used to build kernel-modules after the kernel
> was updated and the komd-package not - this was before vmxnet3
> as example hardly needed for vmware because without network
> yum makes no fun
>
> another example are the nvidia-drivers - for normal users
> it is not acceptable have no GUI after update / reboot
>
> normally the kmod-packages are updated the same time
> as the kernel in stable repos, but you can not guarantee
> this for external repos everytime, especially that the
> mirror you catched is recent enough
But akmods are a very hackish solution to that problem. Building modules on
the end user system sucks on a binary distribution. It drags in the whole
GCC toolchain, kernel-devel and the source code for the modules and the
whole system is a huge kludge, as evidenced also by this thread.
The right solution is for the user to just uncheck the kernel from the list
of packages to update in the PackageKit GUI of choice (be it gnome-
packagekit, KPackageKit or Apper) if the kmod doesn't show up along with it.
It's not rocket science.
Kevin Kofler
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
