SevenMachines <sevenmachi...@yahoo.co.uk> writes: > yes, theres no perfect way to do this.
> I'm not sure what the preferred approach to dealing with dkms modules > is, looking through other dkms modules, the > Depends: linux-headers-generic | linux-headers > approach seems fairly common. the "either you've installed specific > headers for your kernel or i'll install the most common ones" way. > someone who uses openafs would need to make a judgement whether thats a > reasonable thing to do or not. obviously this places responsibility on > diferent kernel users to know that they need to install the correct > headers. I don't believe this is a reasonable thing to do. I think a better approach would be to not fail the postinst when the kernel headers aren't available and instead just display a message telling the user that the module is disabled until the headers are installed. I think to do this properly and handle all the cases, such as building the module after the kernel headers are installed, will need support from the dkms package. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- package openafs-modules-dkms 1.4.11+dfsg-1+ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/487535 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
