This is terrific good news.

Top priority for a "real" Smalltalk system: auto-config that works very reliably across major and minor releases ("very" means fatal errors in any 12 month period over 5 years are less than [ here set a target and publish it and publicly track that performance.]

Builds of Cincom VisualWorks with Seaside 2.x were in the usual tradition of loading Smalltalk (Smalltalkers tend to decry that the St environmen is not well-known or appreciated, but just as well that this non-issue was the in-house�� secret-of-polichinelle ...

The challenge of building Smalltalk may have compared well to Java or C++, but what comfort should have been taken in that?���� That tradional nightmare has been confounding versioning with building.�� My hope had been that Roel Wuyts and SOUL would lead to a solution through a build agent able to backtrack and achieve a build where one was possible given certain minimal constraits and effectively report the build obstacles without ever dropping into a debugger.

Congratulations and this wish: may it almost always build and build well and most often build as intended (and leave - most often - only the in-house developer-engineers living on that bleeding edge.)�� May Pharo soon be the best "mature" Smalltalk environment (regardless of which dialect leads along the bleeding-edge.)

F��licitations & viel Gl��ck !