Re: [desktop] RFD: Can DeMuDi and Desktop Debian unite kernel development efforts?
On 10/23/2002 11:36 AM, Andreas Tille at email@example.com wrote:
> The sense of internal project is to handle *existing* packages in Debian
> and not to develop special packages.
Agreed. See below for further thoughts.
> For instance every subproject is
> very interested in debian-installer. But debian-installer is by no
> means a subproject effort in the first line.
Andreas, I think I understand where you are coming from, and that we are
actually in agreement, but just suffering from a bit of miscommunication.
My idea was not meant to suggest that Debian Desktop become a separate
project from mainstream Debian. I would very much like to see it tightly
integrated into mainstream Debian, as an option that one can choose during
Here is why I suggested linking up kernel development efforts between DeMuDi
and Debian Desktop. Both of us want to apply very similar patchsets to the
standard Debian kernel, although with a few differences. DeMuDi wants some
special ALSA patches from CVS, which doesn't really affect Desktop Debian.
DD might want to apply the supermount patch (maybe), which is probably
irrelevant to DeMuDi. However, there are a number of patches we both would
like to see put into a Debian kernel, which could be made available during
installation, just like the various already existing, different kernel
The idea is that DeMuDi and DD join efforts in terms of testing and
developing our special patchsets - this reduces wasted duplication of
effort. Then, at some appropriate time, we humbly approach the Debian
kernel maintainers and possibily the release manager as well; and say, "Hey
guys, we have a fully tested kernel here which we would like to include with
your various other kernel images as an optional choice during installation.
We have done a lot of work on it already, to hopefully make the kernel's
inclusion easy for you to do. Could you please add it in with the other
official Debian kernel images?"
Andreas, I hope this clarifies any misunderstanding. If you have additional
concerns, or other questions, please comment in reply.