On Sun, Dec 17, 2006 at 10:15:52PM -0500, geoffroy vallee wrote: > Hi all, > > The package creation is based on the kernel version shipped with Debian. I > do not want to change the kernel by default. It is the approach selected by > Dann and i think it is the best one. Debian developers spend a lot of time > to ship a kernel coherent for the distribution, i think it is a bad idea to > want to change that.
The reason for this is that we try to keep all kernels built within Debian on the same kernel version. This means we can all share the same linux-source- package, which is the only place that needs to be patched for legal issues/security fixes, etc. The fact that this is currently 2.6.18 is a temporary thing, and no release of Debian will actually ship with that. Since 3.6 is the latest stable release of systemimager, that is the version that will ship in etch (unfortunately). Since 3.6 requires devfs support, I had to deviate from the single-kernel-source thing to use an older kernel that supports devfs, 2.6.12 (also, unfortunately). So, once 3.8 releases we can actually upload it to sid, and it should track whatever the latest source is. Debian sid usually gets an upload of the newest upstream kernel source within 24 hours of its release. The exception is when we are frozen for a release, like right now. In other words, by the time we can upload systemimager 3.8, we will be able to use a newer kernel. -- dann frazier ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
