[squeak-dev] SqueakTrunk image on build.squeak.org broken?

Edgar J. De Cleene edgardec2005 at gmail.com
Thu Oct 24 21:02:55 UTC 2013




On 7/28/13 3:22 PM, "Frank Shearar" <frank.shearar at gmail.com> wrote:

> It's a term I picked up from work: SqueakTrunk is like a dessicated,
> dried out thing that's quite small, like a dessicated pea. But
> ReleaseSqueakTrunk is like the rehydrated pea, useful for cooking.
> 
> As the package layering work proceeds, and more packages become
> unloadable, I unload them from SqueakTrunk. ReleaseSqueakTrunk takes
> that small SqueakTrunk artifact and reloads all those unloadable
> packages.
> 
> The idea is that people just keep on using the ReleaseSqueakTrunk
> image, and without even realising it, are using a _constructed_ image,
> built up from some small core.
> 
> frank


And when we go bold and use a Core.image?
Our cousins Pharoers build a PharoKernel from sources , great work of Pavel
and Guillermo (and others maybe).

Edgar




More information about the Squeak-dev mailing list