Paul-

I wouldn't count on this for your own needs since you are trying to do something in the near future and I have only a limited amount of time to work on this.  But, it seems to me that building a modular Squeak is a really good use case for me right now, as it puts just the right kinds of stresses on the tools I've been building.  This will take a while, as I really need the third and final piece of Oasis in place to do this easily, and I will be devoting most of my effort on building that and merely using the "modular Squeak" use case as a motivating example.  But the end result is that one would be able to pick any of the Squeak versions, as well as several other dialects, and then assemble the class libraries in a controlled manner for your deliverable.

I've done enough of this so far to know that there will be some tough problems to crack- but I think it can be done.  The case for optimism rests on my currently being able to execute code written for Squeak that is sitting on top of PocketSmalltalk's core class library, running within VisualWorks.  Not that I have every little problem taken care of and a totally seamless solution, but that I can indeed execute the code and use regular programming tools on it- just like we've grown used to doing in regular Smalltalk image land.  On the pessimistic side, there is still a fair amount of substantial and at times difficult work to be done before seamless operation is routine.

Take care!

- les