Upgrading pcmcia modules with self-built kernel

[Bart-Jan Vrielink <bartjan@vrielink.net>]

Hello,

Everytime I do an apt-get dist-upgrade, Debian tries to upgrade
pcmcia-modules-2.2.x, unless I put it on hold. I don't want to upgrade
pcmcia-modules, because it needs to match a specific build of the kernel.

The package kernel-package suggests to set the Debian version to a very
high value when building the kernel-image packages yourself. This won't
work for the pcmcia-modules package, because there also the upstream
package version changes.

Isn't it possible to solve this problem by having two versions of
pcmcia-modules-2.2.x, a -generic one, and a -custom one. Both provide
pcmcia-modules-2.2.x. kernel-image-2.2.x should then be provided by
two packages, a -generic one and a -custom one. This gives:

package: pcmcia-cs
depends: pcmcia-modules

package: pcmcia-modules-2.2.x-generic
provides: pcmcia-modules-2.2.x
depends: kernel-image-2.2.x-generic

package: pcmcia-modules-2.2.x-custom
provides: pcmcia-modules-2.2.x-custom
depends: kernel-image-2.2x-custom

package: kernel-image-2.2.x-generic
provides: kernel-image-2.2.x
conflicts: kernel-image-2.2.x-custom

package: kernel-image-2.2.x-custom
provides: kernel-image-2.2.x
conflicts: kernel-image-2.2.x-generic

The packages kernel-source-2.2.x and pcmcia-source should build the
-custom packages. I don't know if that's possible to combine with the
maintainers using those packages to build the -generic packages.

Do you think this is a sollution for this problem, or is it solvable in
another way ?

-- 
Tot ziens,

Bart-Jan