Thank you much for these infos, Ben!<br>
<br>
This is very interesting, and I really think it would be a good idea to
consider this option, and register ichthux as a CDD on Debian, and
build metapackages for the distro :)<br>
<br>
<br>
<br><br><div><span class="gmail_quote">On Apr 8, 2005 2:45 PM, <b class="gmail_sendername">Ben Armstrong</b> <<a href="mailto:synergism@gmail.com">synergism@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>I've talked to you guys a bit on irc, but for the sake of the<br>archive-reading audience, I am SynrG (<a href="mailto:synrg@debian.org">synrg@debian.org</a>) the leader of<br>the Debian Jr.[0] project.<br><br>I see no reason why Ichthux should be a splinter distribution, a<br>derivative of a derivative (a remastered Knoppix) when it could be<br>entirely or at least mostly mainstream Debian work like Debian Jr. So<br>long as everything you're doing is DFSG[1] free, and every indication<br>from what I have seen so far is that it is, Ichthux qualifies as a<br>CDD[2]. Why don't we look at the tools Custom Debian has written so<br>far and see if we can hack together a CD mastered straight from Debian<br>with them? The tools in sid already are a bit behind the development<br>curve, so you might want to look over the debian-custom[3] mailing<br>list and figure out what's current. I think simple-cdd[4] might be a<br>good place to start.<br><br>Being mainstream means less customization work for the Ichthux<br>developers, and broader support for the Ichthux users. Instead of<br>relying solely on Ichthux for filing bugs and discussing problems,<br>they could confidently draw on the broader Debian user and developer<br>community for support, not having to be worried about things being<br>done the "Ichthux way" instead of the "Debian way". With derivatives,<br>a typical user problem is handled like this:<br><br>bar user: I have a problem with package foo when I use it in your<br>derivative bar, can you help?<br><br>bar developer: Sorry, I would really like to, but foo isn't in bar. I<br>have never used it, and really don't have the time. Why don't you<br>speak to the foo maintainer?<br><br>bar user: OK. Foo maintainer, can you help?<br><br>foo maintainer: Sorry, I would really like to, but I've never used<br>bar, and I don't have the time to do a bar install. Have you talked<br>to the bar developers?<br><br>Everyone means well, but the poor bar user falls between the cracks.<br>With a CDD it doesn't have to be this way. The Ichthux user can file<br>bugs directly on their favourite packages (whether they are<br>Ichthux-related or not) and the developer won't have to worry about<br>Ichthux messing with the system in ways that violate Debian policy.<br>If the developer has to talk to another developer, it will be within<br>Debian, not in some other project the developer has never heard of.<br><br>Ben<br>[0] <a href="http://www.debian.org/devel/debian-jr">http://www.debian.org/devel/debian-jr</a><br>[1] Debian Free Software Guidelines <a href="http://www.debian.org/social_contract">http://www.debian.org/social_contract</a><br>[2] Custom Debian Distribution <a href="http://wiki.debian.net/index.cgi?CustomDebian">http://wiki.debian.net/index.cgi?CustomDebian</a><br>[3] <a href="http://lists.debian.org/debian-custom">http://lists.debian.org/debian-custom</a><br>[4] deb <a href="http://debian-np.alioth.debian.org/debian">http://debian-np.alioth.debian.org/debian</a> unstable main<br>_______________________________________________<br>Ichthux-devel mailing list<br><a href="mailto:Ichthux-devel@crosswire.org">Ichthux-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/ichthux-devel">http://www.crosswire.org/mailman/listinfo/ichthux-devel</a><br></blockquote></div><br>