<br><br><div class="gmail_quote">On Sun, Apr 19, 2009 at 12:38 PM, Bert Freudenberg <span dir="ltr"><<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 19.04.2009, at 20:03, Matej Kosik wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bert Freudenberg wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Even Debian did not object to the licensing anymore - it's in non-free<br>
because they do not like the idea of purely image-based development.<br>
Which is one of the reason why I'm only shooting for VM packages for now.<br>
</blockquote>
<br>
This approach does not make sense to me. What is the point of including<br>
Squeak VM to Debian without image(s) and sources? It would mean that<br>
half of the things is distributed in one way (through Debian<br>
repositories) and other things (images & sources) are distributed in<br>
other ways (users have to hunt for right kind of image and right kind of<br>
sources on the web). In my opinion, this approach is chaotic.<br>
<br>
Including Squeak VM to Debian repositories could have been done anytime.<br>
I did try to do that because it alone makes little sense (my opinion).<br>
</blockquote>
<br>
<br></div></div>
In my opinion it does, and it solves the hardest problem first (see my reply to Subbu).<br>
<br>
Going for all-or-nothing just prolongs the current undesirable situation unnecessarily. I'm proposing to go step by step. Of course, the people actually doing the work will decide on their own which path to take.<br>
<font color="#888888">
<br>
- Bert -</font></blockquote><div><br></div><div>IMO the most sensible thing to include in a linux distro is a VM with a minimal headless scripting image that has the capability of loading packages to build whatever image one might want. This would allow one to write #!/bin/squeak scripts against some minimal base. But there is a lot of work here:</div>
<div>- defining an elegant or pleasant to use file system interface instead of the rather broken one we have now (FileDirectory and FileStream have a horrible API, verbose, unintuitive, incomplete; file streams are slow (no buffering))</div>
<div>- defining a base scripting library (i.e. defining something minimal that is useful in a scripting context and well-designed enough to last)</div><div>- providing python-quality documentation and breadth of functionality</div>
<div><br></div><div><br></div><div>But I'm saying this largely in ignorance of 3.10 and lack of experience with Rio which definitely looks to be a step in the right direction re verbosity.</div><div><br></div><div>2¢</div>
<div>Eliot</div></div><br>