Re: creating binary modules
>>"Adrian" == Adrian Bridgett <email@example.com> writes:
Adrian> b) the "*-modules-source" maintainers grab kernel-source-*, untar that and
Adrian> /usr/src/<their-module>" tarballs, run make-kpkg ... modules_image, and
Adrian> then upload the results.
Adrian> Points for b)
Adrian> - module maintainers have to download kernel-source (~12MB)
Just get the diffs, and you do not need the kernel-source
Adrian> - module maintainers may not have easy access to box
Adrian> In both cases, there is the difficult of keeping things up-to-date -
Adrian> for b) every *-module-source maintainer has to
Adrian> watch out for new versions of kernel-image-*. 
Well, isn't that inherent in any synchronization scheme?
Cats are smarter than dogs. You can't make eight cats pull a sled
through the snow.
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C