I maintain a kernel module package (eeepc-acpi-source) that has been merged into the mainline Linux kernel as of version 2.6.26, and has had features added, bugs fixed, etc.
The standalone module is still useful for the 2.6.25 kernel, but will be unnecessary in lenny+1. I'd like to somehow indicate that the resulting eeepc-acpi-modules-NNN packages are obsolete when NNN >= 2.6.26. 1. I can make the package fail to build (under module-assistant or make-kpkg) when the kernel version is recent enough. I don't know whether this kind of "conditional build failure" is acceptable practice, but it would keep useless .debs out of the archive. 2. I can make the package continue to build, but have the resulting .deb conflict with, as well as depend on, the corresponding linux-image package, so it becomes uninstallable. 3. I can do nothing at the package level, and rely on "educating users" to not use this package for recent kernels. I'd appreciate any guidance. Cheers, Eric -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
