The DKMS scripts assume that a package update will install software to build
at /usr/src but in a different directory. So, an update to a package that
is just a change in the debian build stuff but not the source proper will
cause a problem, since DKMS will remove the old source dir after the new
source dir is already unpacked. If they are the same, it breaks. We fix this
problem by simply informing DKMS that the source version include the debian
version info as well. So for example, instead of 0.11.2, DKMS would see
0.11.2-5.2tmi.
set -e
NAME=xxPACKAGExx
-VERSION=xxPKGVERxx
+VERSION=xxDEBVERxx
case "$1" in
configure)
#!/bin/sh
NAME=xxPACKAGExx
-VERSION=xxPKGVERxx
+VERSION=xxDEBVERxx
set -e
#!/bin/sh
NAME=xxPACKAGExx
-VERSION=xxPKGVERxx
+VERSION=xxDEBVERxx
set -e
# This file may have to be extensively modified
package = xxPACKAGExx
-inst_dir = debian/tmp/usr/src/xxPACKAGExx-xxPKGVERxx
+inst_dir = debian/tmp/usr/src/xxPACKAGExx-xxDEBVERxx
install_dir = install -d -m 755
install_file = install -m 644