[Build-common-hackers] generating files in debian/

[IOhannes m zmoelnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi all,

i'm currently trying to create CDBS snippets for packaging
kernel-modules, both traditional "-source" packages and modern "-dkms"
packages.

i started with dkms rules, and now i have a number of questions. here is
one:


- - dkms packages are supposed to install into /usr/src/<pkgname>-<version>
now i do believe that once a package is properly packaged, a new
upstream release should involve only a minimal set of changes in debian/
apart from debian/changelog and a possible update of debian/patches/, i
see no need to touch any other file (given that nothing has changed
dramatically in the upstream sources). e.g. having to change
<pkgname>.install to reflect the new upstream version is superfluous.
so the idea is to autogenerate things whenever possible.
e.g. one could generate debian/<pkgname>.install from
debian/<pkgname>.install.in, by doing simple substitution (in my case i
would substitute something like @VERSION@ for $(DEB_UPSTREAM_VERSION))

now i see 2 possible issues:
- - is this allowed at all? e.g. afair debian/control MUST NOT be
generated automatically, does this also apply to other files normally
found (and searched for!) in debian/
- - if it were allowed, what would be a good strategy to make this as
modular as possible? e.g. imagine snippetX would like to generate
debian/<pkgname>.install from debian/<pkgname>.install.in and snippetY
would like to do so as well. i think the two substitutions should both
be applied, but how do i do this properly?

mfasdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1K2A8ACgkQkX2Xpv6ydvTxTwCghvl/8fj18vphQAqV53HSJUZQ
t6oAoNAKOfXl6sFdir5bWgwok/WDmsBB
=Yvd5
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.alioth.debian.org/pipermail/build-common-hackers/attachments/20110203/1a8095d0/attachment.bin>