I think so.  The two use-cases addressed are: 1) fixed-configuration
and 2) on-going development.

The head release is for on-going development -- merges the latest
versions in a trunk-style update process for the project.

Fixed-configuration documents a starting image onto which you can
install specific-version packages known to work together.  A
convenience feature allows the publisher to one-click publish update
patches to such a fixed-configuration.

These two use-cases cover possibly 95% of what the overall community
requires.  The spirit of Squeak is to have little code go a long way.


On Mon, Mar 12, 2012 at 5:51 PM, Frank Shearar <frank.shearar at gmail.com> wrote:
> On 12 March 2012 21:23, Chris Muller <asqueaker at gmail.com> wrote:
>>> I realise we're agreeing on the meat of the issue, so feel free to
>>> ignore the following: the essential difference between writing a load
>>> script and using Metacello is that if one of the packages I use - Bar
>>> - upgrades something that _it_ uses (Baz) (and about which I don't
>>> care), then without my doing anything more than saying "my package now
>>> uses Bar 2", everything still Just Works. It delegates the
>>> responsibility for building Bar to where it belongs, with the Bar
>>> developers.
>>
>> This is exactly how SM handles it too, there is no difference here.
>> The "head" release of Baz would load the head release of Bar. By
>> selecting "install" on the head release, it merges the latest version
>> of Baz without having to care about it.
>>
>> http://wiki.squeak.org/squeak/6182
>
> But you can also fix the version of Baz, right? (Otherwise you
> don't/can't know what you're actually building.)
>
> frank