On Fri, Sep 13, 2002 at 06:21:15PM +0200, Bastian Kleineidam wrote: > On Fri, Sep 13, 2002 at 06:01:05PM +0200, Sven LUTHER wrote: > > On Fri, Sep 13, 2002 at 05:15:59PM +0200, Bastian Kleineidam wrote: > > > > How do other module packages handle this, do someone know at a good such > > > > package i could use as example ? > > > The current ALSA packages (apt-cache show alsa-source) are doing it > > > this way. > > > > Ok, i will look at it ... > > > > Mmm is there not a smaller example to look at ? I only have a slow modem > > line. > Here are some more: nvidia-kernel-src, cryptoapi-core-source, > cryptoloop-source, i2c-source, lm-sensors-source > > > My idea was that people would do : > > > > apt-get source unicorn > > cd unicorn-0.3.4 > > edit debian/rules and modify the KERNEL_VERSION variable > > dpkg-buildpackage ... > > With the above packages, it would be like this: > > apt-get install unicorn-source > cd /usr/src && tar xzvf unicorn-x.y.tar.gz > cd /usr/src/kernel-source-2.4.18 && make-kpkg modules_image > insmod unicorn
Mmm, yes, but there is a difference, the above stuff is available as a kernel patch or something, while the unicorn driver comes in a standalone tarball, and is not integrated within the kernel build system. So i don't believe it will be easily made to work with kernel-package or other kernel stuff. This is why i choose to build it as a single binary package. I am not sure, but maybe this situation means that the unicorn driver does not enter in the 'difficult to build for different kernels' situation ? (well mostly, a make, make install works fine for the upstream tarball). Friendly, Sven Luther
