Iterative development with MCConfigurations

Chris Muller chris at funkyobjects.org
Thu Dec 14 02:34:39 UTC 2006


What is a best practice for doing iterative development with
MCConfigurations?

I want to be able to make plenty of short, incremental improvements,
with a map defining the stable combination of packages each time.

I found Cees' great "MCConfigurations quick how-to"

 
http://lists.squeakfoundation.org/pipermail/squeak-dev/2005-November/098181.html

He seems to say this sort of development is overrated (I'm interpreting
his words with my own word).

But even if I didn't want to be conservative and have lots of
small-step maps I can easily roll-back to, I still want to at least be
able to post the continuously improving software to SqueakSource.  When
posting though, it doesn't overlay the existing configuration with that
name, instead gives you an error "Found".  SqueakSource doesn't seem to
be aware of configurations so you can select and delete them.

So that leaves versioning.  I have not seen a way for configurations to
be "versioned," but since ancestry isn't really necessary for
configurations maybe this really just amounts to me using my own naming
scheme that includes an incrementing number..?

What are some good practices?




More information about the Squeak-dev mailing list