On Mon, Sep 26, 2011 at 3:07 PM, Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote: > On Mon, 2011-09-26 at 15:00 -0500, Richard Shaw wrote: >> > 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? > > Then maybe we could add some logic into yum that (a)kmod could come with > a configuration file which does this (ie: blocking the kernel from > updating until the corresponding (a)kmod is available). I would think this has been discussed before... But to play devil's advocate. What if someone is running a modified kernel? Sure if they know how to do that then they should know how to update their drivers prior to installing it, but in that case akmods is more of a package/tool of convenience. Richard -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
