How to force dkms_autoinstaller build and install even when status=installed-weak

[Matt Domsch]

On Wed, May 30, 2007 at 08:47:51AM +0700, Fajar A. Nugraha wrote:
> Hi Matt,
> 
> Matt Domsch wrote:
> > On Fri, May 25, 2007 at 01:10:49PM +0700, Fajar A. Nugraha wrote:
> >   
> >> So, for modules like qla2xxx, this means that when a kernel update
> >> occurs, weak-modules will kick in, making dkms_autoinstaller refuse to
> >> rebuild and install that particular version, but the kernel will not use
> >> the weak-update.
> >>
> >>     
> > Yeah, not really what you want.  Built-in should override
> > weak-updates, as built-in *should* be newer than weak-updates, but
> > there's no actual code in module-init-tools to check that.
> >
> >   
> After giving some thoughts, I think that the best solution might be to
> create a local version of module-init-tools that removes
> /sbin/weak-modules altogether, and replace it with (perhaps) symlink to
> /bin/true. The reasoning behind this is :
> 
> - As you mentioned, built-in should override weak-updates. At least
> Redhat thinks so, although Suse folks don't.
> - Built-in modules is included with kernel updates
> - Non built-in kernel-module RPMs (the ones I need anyway) can be
> converted to dkms modules
> - The extra boot time required to build a kernel module is not issue
> 
> Which means there's no need for /sbin/weak-modules.
> What do you think?

Seems fair for your purposes.

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com