Thanks for replying Jeremy, comments on your suggestions inlined. For anyone interrested the complete packages (including .orig.tar.gz) are available in http://nthomas.free.fr/LiS
But my trouble remains : lintian -i lis_2.16.16-2.dsc E: lis source: package-uses-debhelper-but-lacks-build-depends N: N: If a package uses debhelper, it must declare a Build-Depends on N: debhelper. N: but lis_2.16.16-2.dsc is: ------------------------------------------------------------------ Format: 1.0 Source: lis Version: 2.16.16-2 Binary: kernel-lis-modules-2.4.26-1-k7-smp, kernel-lis-modules-2.4.26-1-386, kernel-lis-modules-2.4.26-1-686-smp, lis-doc, kernel-lis-modules-2.4.26-1-k7, lis, kernel-lis-modules-2.4.26-1-686, lis-dev, kernel-lis-modules-2.4.26-1-k6, kernel-lis-modules-2.4.26-1-586tsc Maintainer: Nicolas THOMAS <[EMAIL PROTECTED]> Architecture: any Standards-Version: 3.6.1 Build-Depends: debhelper (>> 4.0.0), kernel-build-2.4.26-1, dbs, m4 Files: 082c8612dce46236282b97d8af4c3f01 792684 lis_2.16.16.orig.tar.gz c5c53afc74063dfa91c35939b390f69f 10461 lis_2.16.16-2.diff.gz ------------------------------------------------------------------ It as a build-depends on debhelper !! what do I miss ?? More inlined : Quoting Jeremy Lainé <[EMAIL PROTECTED]>: > Hi again Thomas, > > I just had a look at your control file.. it's HUGE as you define all the > kernel-lis-modules-2.4.26-1-(386|586tsc|etc..) packages! I suggest you > take a look at how alsa or pcmcia-cs are packaged and create an > "lis-source" package in your control file. > > You should not be building all these different flavours from > your main control file. What you want to do is build : lis, lis-dev, > lis-doc, lis-source. The "lis-source" package is the one that will be > used to build the actual kernel modules. To do so you will provide a > template called "lis-source.control" in your main package which will > define the various kernel module packages. Once again, I recommend you > take a look at how ALSA or the PCMCIA packages are built! What I want is to be able to provide binary packages for debian "official" kernels for now own the automated creation of a big control file and .(pre|post)inst is working. I don't believe it's against policy (correct me if I'm wrong) but fully agree to have a close look at your proposal to easily allow anyone to build modules for it's own kernel. I2C for 2.4 kernels use a similar approach. Anyway I do not see how all this is related to the lintian error .. I first have to work on packaging 2.16.18 version then I'll have a deep look at making a lis-source and make-kpkg template. Thanks > > Cheers, > Jeremy > > -- > http://www.jerryweb.org/ : JerryWeb.org > http://sailcut.sourceforge.net/ : Sailcut CAD > http://mpf70.sourceforge.net/ : MPman MP-F70 support for Linux > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > --
