[aur-general] kernel updates render package obsolete
m.sujith at gmail.com
Tue Nov 18 07:22:47 EST 2008
Aaron Griffin wrote:
> On Mon, Nov 17, 2008 at 10:47 AM, Mads Michelsen <chochem at gmail.com> wrote:
> > So I guess my questions are:
> > 1) Is there some way around the module becoming outdated with each and
> > every kernel update? and if not
> Such is the pain of maintaining out-of-tree kernel modules. It sucks, I know.
> One thing that we do with our kernel modules, to make this easier, is
> we set the version to "2.6.27" instead of "184.108.40.206" so that when .9
> is released, we don't need to rebuild all modules (they still need to
> be tested, however)
That's just trying to circumvent the restrictions that the kernel
imposes on out-of-tree modules.
A kernel API could be changed between minor versions too, and if a module uses a newer
API call with older values, it would result in an oops.
More information about the aur-general