On Thu, 03 Mar 2005 23:26:44 +0100, Robert Millan writes: >Did you try on binary-arch packages?
no, i think that was part of the mistake. but moot anyway as
the tun-source package is not arch-specific...
>> but coming back to the main point: the only /real/ fix that i can
>> see would be to have the kernel module building environment check
>> build-dependencies for modules. any hackery on the outside -source
>> package is going to be exactly that, an ugly brittle hack.
>
>Why can't you add them to the kernel module's build-depends? I recall the
>debian/control file was
>shared and autogenerated or something, but nothing stops you from changing
>that.
the build-dependency *is* there (since incorporating your other suggestions),
but it doesn't do any good: as the kernel building process runs
debian/rules directly, there's nobody to actually look at the build-depends
in the control file.
even if somebody manually ran apt-get build-dep
tun-module-${kpkg:Kernel-Version}, apt-get wouldn't know where to look for the
build-dep info because
the archives don't know about this locally built tun-module-thingie...
dpkg-buildpackage -D/dpkg-checkbuilddeps would at least flag a problem.
hmm, should I add that to the configure target of the module package?
regards
az
--
+ Alexander Zangerl + DSA 42BD645D + (RSA 5B586291)
Never trust a computer you can't lift. - Stan Masor
pgpfGIL8bQnCW.pgp
Description: PGP signature
