Joshua Gargus wrote:
> Douglas Brebner wrote:
>> Joshua Gargus wrote:
>>   
>> Isn't keeping MC in the trunk directly contradictory to the whole point
>> of seperating the image into packages and splitting them out? 
>
> No.  It will still be loadable/unloadable; it will be included for
> convenience.  You could create a Squeak image without a compiler too,
> but this would be inconvenient for the "default" Squeak image (the one
> you first find when looking on squeak.org).
>
Conveniently structured images build from packages is what Kieths build
tool is for.
>> Won't it
>> also make using MC in other smalltalks gratituously harder?
>>
>>   
>
> I don't see why.  All that it means for a package to be "in the trunk"
> is to be in a particular Monticello repository.  In order for a
> package to be compatible across Squeak versions (and even with other
> Smalltalks), somebody has to put in effort.  The effort required is
> not reduced by simply storing the package in a repository "outside the
> trunk".
>
I think there's some confusion here about what "in the trunk" means.
Some people think it means to be kept in the mainline image.
Others think it means to be in the Squeak.org repository.

Exactly which is it?