Hi Junichi,

I'm starting a new thread, as we are turning page :)

JU> Condolences.
JU> 
JU> I've just subscribed to the mailing list and the first major thread is
JU> this, a coincidence.
JU> 

Well, it seems really you're the Deus Ex Machina from Debian then.. :)

JU> Anyway, I'm interested in merging what's available in DeMuDi into
JU> Debian proper, and getting crufty frameworks polished, and
JU> up-to-speed.

That's  perfectly in  the spirit of  A/DeMuDi;  as far as was possible
I've always tried to upload back to Debian what was done in A/DeMuDi.

One big obstacle is  that  I'm not yet a  DD,  though I've passed  the
tests of the NM process almost one year ago, see:

https://nm.debian.org/nmstatus.php?email=free%40agnula.org

I was put on hold  because my GPG  subkey was expired. I've created  a
new one and pinged the DAMs a couple of times, no reply :/

Honestly I never understood why such a pain..

I have   a few packages  in  the  archive yet,  and  I  find it  a bit
difficult to  maintain them (or upload new  ones), as I always need to
bother some DD to sponsor me. So I often end up using mentors.d.n..

JU> 1. patched kernels -- they can enter Debian as tailored kernels,
JU>    probably after a few disagreements with FTP team and
JU>    debian-installer team for having too many kernel flavors
JU>

Having the kernel in the archive  would be great, but even maintaining
it outside  it's   not bad,  especially   once  that  all kernel-patch
packages of the case are in the pool.

Note   also that  the    most   important  patch  for   A/DeMuDi,  the
realtime-preempt one, usually  doesn't   apply cleanly on   the  patch
Debian kernel source, and  would require some modifications (however I
recently noticed that since the  latest 2.6.15, it applies cleanly  on
Debian sources too).

JU> 2. patched packages -- they can enter Debian with patches merged,
JU>    probably having a coordinated effort using debian-multimedia ML as
JU>    a place for coordination
JU> 

Sure.  Actually there  are very few   patched packages, for most  I've
submitted bug to the BTS, but I'd like the divergence to be eventually
zero.

JU> 3. CDs -- they probably need to be hosted outside of Debian, since
JU>    they will be chunky.
JU>

This is true for any CDD, at the moment. Till  the concept of CDD gets
really integrated into Debian, it will be  difficult to have CD images
in.

JU> 4. scripts to generate the CDs -- they can be packaged into Debian, so
JU>    that anyone could theoretically build a CDD from Debian sources.
JU> 

I'd love to see this, but it would  require some work. Probably adding
some  features  to    existing package like    debian-cd  would almost
eliminate the need of such scripts at all.

Cheers,

Free