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

Nicolas Cellier nicolas.cellier.aka.nice at gmail.com
Fri Oct 25 12:06:43 UTC 2013


Yes, Pharo is doing a great work of simplification.
On the other hand, it deliberately has zero requirements to make removed
parts reloadable, so the task is a bit easier...


2013/10/25 Frank Shearar <frank.shearar at gmail.com>

> On 24 October 2013 22:02, Edgar J. De Cleene <edgardec2005 at gmail.com>
> wrote:
> >
> >
> >
> > 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).
>
> When I have time, basically. I reconstructed the base image from
> scratch recently, and haven't had a chance to re-rip out Nebraska,
> Universes, and all the other bits I'd previously removed.
>
> I'm very happy to see Pharo do this work. Kudos to Pavel & Guille &
> friends!
>
> frank
>
> > Edgar
> >
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20131025/3511a750/attachment.htm


More information about the Squeak-dev mailing list