On Mon, Sep 26, 2011 at 2:54 PM, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > 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. Yes, but it works :) > 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. No, it's not rocket science, but it does require manual intervention on the part of the user who may or may not understand the relationship between the kmod driver and the kernel. Shouldn't updating (by kmod, or akmod) be more or less transparent to the end user? Richard -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
