Frank, this is so great.  Everyone wants a smaller image for server
processing but keeping "rich" images for clients and development.  I
love the methodical way you've come about to producing both, leaning
on the systems own tests to ensure quality is maintained every step of
the way.  Kudos!

> ... snip ...
> Sure! Questions are always welcome!

Chris Cunningham posed an excellent question -- does anyone know
whether we could take a SqueakTrunk (core) image, load selective
packages into it but still keep up-to-date with trunk?

>From what we've learned from Levente about the update-#; it's the sum
total of all version numbers across all loaded packages and the trunk
update uses that number to determine what updates are needed to move
the image forward.

With packages unloaded the trunk update process would seem to break
down for that image, is that right?

If we can't update a core/custom images, it creates a trade-off
situation right off the bat.  A smaller image, yes, but one that can
only be manually patched.  Is there any way to maintain the best of
both worlds?