<br><br><div class="gmail_quote">On Sat, Nov 8, 2008 at 2:37 PM, Holger Levsen <span dir="ltr"><<a href="mailto:holger@layer-acht.org">holger@layer-acht.org</a>></span> wrote:<br><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>
thanks from me to Jecel for clarifications too!<br>
<br>
On Friday 07 November 2008 19:45, Jonas Smedegaard wrote:<br>
> The Squeak image "Etoys" (the only one currently packaged officially for<br>
> Debian) is in "non-free" due to ftpmasters judging it not possible for<br>
> the security team to maintain throughout the (multiple year long)<br>
> lifespan of a Debian release.<br>
<br>
IIRC/IIUC this is one aspect why the ftpmasters didnt accept it in main. More<br>
generally said, (IIRC) it's because the impossibility to bootstrap etoys.<br>
Even though the etoys developers "don't do it" and the stateful VM (or rather<br>
patches to it) is/are the prefered form of modification.<br>
<br>
And while I dont agree with the position they are taking (should I<br>
say, "anymore"..) I can understand why they do: because it makes sense and<br>
(probably also) because this is like it always was: traditional software has<br>
to have the ability to be bootstrapped or build.<br>
<br>
Squeak is special in this case and I dare to say "new". (I know it was started<br>
in the 70ties :) But not all people do.)<br>
<br>
So my planned approach to get it into main in the long run, is to start a<br>
general discussion in Debian about this kind of software, thus stopping to<br>
special case squeak.<br>
<br>
But as you might know (or not), Debian is in the process of releasing Lenny<br>
atm, so I don't think it's a good time to start philosophical discussions<br>
now. We should rather concentrate on fixing those last bugs and getting Lenny<br>
out, so that we concentrate again on fancy new stuff! :)<br>
<br>
<br>
I was also happy to read Greg Dekoenigsberg mail in this tread and wonder the<br>
same: whether there are any lessons that can be shared between Fedora and<br>
Debian maintainers in this case. And how. My approach is to create a<br>
comprehensible document (quoted by Jonas in this thread) explaining the<br>
issue(s).<br>
</blockquote><div><br>Holger,<br><br>Thanks for taking the time to think about and explain this issues clearly from a packager/distribution point of view.<br><br>david <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
regards,<br>
<font color="#888888"> Holger<br>
</font><br>_______________________________________________<br>
IAEP -- It's An Education Project (not a laptop project!)<br>
<a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br></blockquote></div><br>