BTW is one of the Pharo builds a minimal build?
In case we have Smalltalk unloadAllPackages
working
Frank or somebody else can set up a script for www.squeakci.org to produce a minimal release.
Actually the goal might not be far away....
--Hannes
On 12/28/12, H. Hirzel hannes.hirzel@gmail.com wrote:
Yes, Edgar,
I assume everybody agrees with going for a smaller base image and loading packages on top of it. In particular as we now have this nice www.squeakci.org infrastructure.
We need to get
Smalltalk unloadAllPackages
to work again in 4.4. See the corresponding thread.
--Hannes
On 12/28/12, Edgar J. De Cleene edgardec2005@gmail.com wrote:
On 12/27/12 8:34 AM, "Frank Shearar" frank.shearar@gmail.com wrote:
I also think that the ReleaseBuilder stuff doesn't belong in the Trunk image and should be maintained externally. (MAYBE it could be loaded into an image just as part of the release process, but really I'd like scaffolding - ConfigurationOf packages, ReleaseBuilder stuff, etc. - to not be in the image at all.)
For years I beg we MUST have a SqueakCore .
I made 3.10 and proud of it, the first step in modular Squeak. Can't made 3.11... I attach the last script for it, see unloadSomeMore. I hope you success taking the code and improving. Made a SqueakCore and any Squeaker could decide which packages load later. Also is time to have new .sources and if we have a cleaner and small system ....
If you have time see the .cs. I apply it to Squeak , Cuis and Pharo and you could see the results in http://squeakros.org/3dot11 http://squeakros.org/Cuis3dot2 http://squeakros.org/Pharo1dot4
If we have a SqueakKernel , as Pavel made for Pharo and sure could build for us if we send a nice mail to he, could load the classes we need
Edgar