<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Luxi Sans'; font-size:11pt; font-weight:400; font-style:normal;">On April 15, 2009, Bert Freudenberg wrote:<br>
<<snip>><br>
> Maybe having a mailing list specifically for maintainers would be<br>
> useful? <br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Yes! We could suggest to Tim we create squeak-etoys-maintainers list at squeakland (or maybe it belongs to squeak)?, and advertise it's existence on the main distros. We can offer to the subscribed maintainers that:<br>
- it would be reasonably low volume<br>
- the squeak and etoys community would report distro-specific problems <br>
- the squeak and etoys community would monitor it for questions and try to help<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> But even just tracking down what packages are already out<br>
> there, who is maintaining them etc. would be very valuable. And<br>
> monitoring the bug trackers, participating on the distro-maintainers<br>
> lists etc. Here is just a short list for squeak packages in various<br>
> distros:<br>
><br>
> Debian:<br>
> http://packages.debian.org/search?keywords=squeak-vm<br>
> Fedora:<br>
> https://admin.fedoraproject.org/pkgdb/packages/name/squeak-vm<br>
> Ubuntu:<br>
> https://launchpad.net/ubuntu/+source/squeak-vm<br>
> OpenSuSE:<br>
> http://download.opensuse.org/repositories/devel:/languages:/smalltalk/openS<br>
>USE_11.0/repodata/repoview/Squeak-0-3.9.8-288.1.html Gentoo:<br>
> http://gentoo-portage.com/dev-lang/squeak<br>
> Arch:<br>
> http://aur.archlinux.org/packages.php?ID=13021<br>
><br>
> The good news is that once there are "good" packages in the major<br>
> Linux distributions, the smaller ones can follow suite much more<br>
> easily. The big issues of e.g. what build dependencies exist are<br>
> solved by then, and everyone can learn from each other.<br>
><br>
> Squeakers have been pretty much ignorant of the larger open-source<br>
> community in the past. But I think there is a lot to be gained by<br>
> becoming a proper part of it. I have been working towards that goal<br>
> for a while now, in particular as part of the OLPC / Sugar development<br>
> efforts. Etoys is distributed as part of Sugar and depends on an up-to-<br>
> date Squeak-VM package, so we do have allies in the Sugar maintainers.<br>
> And everyone can help - as I wrote above, no deep VM knowledge is<br>
> necessary to monitor bug trackers or keep contact with the maintainers.<br>
><br>
> So there. Who else wants to get involved?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I use openSuSE, so I can contact the opensuse people. I was in fact thinking I try to build Squeak for OpenSuse (they have well published and documented build system), but cannot commit to that much time.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>So I think we should first create the list ,come up with a standard (nothing too complicated) email that we send to the main distros lists. <br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Cross-posting this to squeakland software list...<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Milan<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>><br>
> - Bert -<br>
><br>
> PS: Note that I am primarily concerned with the VM packages for now.<br>
> Packaging images is a somewhat separate issue, simpler because no<br>
> dependencies are involved, and at the same time harder because there<br>
> is no established practice of where to put them in the file system<br>
> hierarchy. There used to be the license issue with images, too, but we<br>
> should shoot for proper packaging with the license-clean upcoming 4.0<br>
> release. If you want to discuss this, please start a different thread.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p></body></html>