On Sun, Feb 17, 2008 at 06:51:49PM -0600, Matt Domsch wrote:
On Sun, Feb 17, 2008 at 02:17:16PM -0500, Jeremy Katz wrote:
On Sat, 2008-02-16 at 09:53 -0600, Matt Domsch wrote:
DKMS would like to have the opportunity to run it's auto-rebuilder/installer after a new kernel RPM has been installed, without having to wait for a system restart to run it. Likewise, when a kernel RPM is removed, it would like to be able to run to remove modules managed by it.
When we talked about this, I guess at FUDCon last year, didn't we end up agreeing to have this stuff done from /sbin/new-kernel-pkg? Keeping the implementation of things in the kernel package itself simple is a good thing and carrying around the explicit scripts in the kernel package's scriptlets doesn't help there.
I can put it in /sbin/new-kernel-pkg, but need to extend that to be called in %posttrans then, which it isn't now. %posttrans guarantees me it gets called after both kernel and kernel-devel are installed, when they're installed in the same transaction.
is there any reason why we can't just move %post to %posttrans? Current %post contains:
#!/bin/sh if [ `uname -i` == "x86_64" -o `uname -i` == "i386" ] && [ -f /etc/sysconfig/kernel ]; then /bin/sed -i -e 's/^DEFAULTKERNEL=kernel-smp$/DEFAULTKERNEL=kernel/' /etc/sysconfig/kernel || exit $? fi /sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install 2.6.23.15-137.fc8 || exit $? #if [ -x /sbin/weak-modules ] #then # /sbin/weak-modules --add-kernel 2.6.23.15-137.fc8 || exit $? #fi