> As I understand it, with Metacello you can specify something like:
> "take the last stable version known to work in trunk 4.2"

My problem with this concept is that we are beating ourselves with our
own English ambiguity.  What, exactly, does "stable" and "known to
work" mean?  Honestly, the only meaning I take from those phrases is
just, "compatible," (as in, these set of package-versions are
compatible with each other) which is exactly what I already get with a
simple MC Configuration or SAR.

So whether I load a simplistic MC Configuration named, "4.2
Compatible" or a complex Metacello configuration declared as, "last
stable version known to work in trunk 4.2", I'm still likely to go
looking at merging newer versions if I care to; or not if I don't.  In
either case, Metacello didn't save me anything, but it did bring bulk
and complexity to my packaging system.

> It could seem like an advantage.
> But there is no magic, someone has to hardcode some version numbers somewhere.

Right, but even Berts original MC Configurations UI takes the tedium
out of that.  It's basically one-click..