[ANN] Monticello Versioning

Avi Bryant avi at beta4.com
Fri Jul 25 02:57:42 UTC 2003


On Thu, 24 Jul 2003, Daniel Vainsencher wrote:

> BTW, from a quick glance at MC, seems to me that the following might be
> removable -
> * Tests
> * UI
> * Mocks
> * Storing
> * Merging
> * Patching?

Bootstrap, Tests, Mocks for sure.  UI and Merging could go if this were
just for users of packages, not developers.  Storing is actually used
right now for loading as well, although that doesn't have to be true if
we're trying to slim down.

Base, Modelling, Loading, Patching, and Versioning would definitely be
needed.  Patching is used during updates (a patch is produced between the
image and the version you're loading, and then that patch is applied to
the image).  That's about 30 classes, whatever that means.

But is it really that bad to just distribute stuff as .mcv, and force
people to load Monticello if they want to use it?



More information about the Squeak-dev mailing list