I (re)packaged rtlinux version 3.2-pre2 a few months ago to make it work with make-kpkg, so a modules package and a patched kernel package are automatically built.
One problem that i couldn't solve is with the debconf script, as one of the questions was not always asked, if I remember. Could you upload this as a NMU (is this correct?), as I'm planning to apply as a new debian developer :) The source package is available at [1] (sorry, there's no anonymous cvs acces still, but if you want, I can send you the whole source via email) 1. http://lafarga.upc.edu/scm/cvsweb.php/packages/rtlinux-3.2-pre2/?cvsroot=gnupcix read you, Lluis El Tue, Sep 27, 2005 at 09:48:35AM -0700, Debian Bug Tracking System ens deleit? amb les seg?ents paraules: > One of the reasons for using Debian is the lack of messyness when having > everything installed with packages, including kernel images. > > For normal kernels, make-kpkg from kernel-package makes a terrific job > at creating new kernel-image packages with friends. > > In a perfect world it should be possible to easily create those packages > for RTLinux patched kernels too. However the README.Debian gives no help > on how it could be done. > > Although I don't fully understand what is done when a rtlinux patch is > applied to the kernel I assume it messes to much with the core internals > to be enough for RTLinux to provide a /usr/src/modules/ directory, but > the modules should be able to build from such a directory? > > Creating a simple shell script to check that kernel version and patch > versions correspond would help. And after that patching the kernel to > produce a tree suitable to run make-kpkg in. > > I'm willing to help. Please tell me how. -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
