[squeak-dev] Re: About unloading of packages in the most recent Squeak 4.1 trunk

Hannes Hirzel hannes.hirzel at gmail.com
Thu Aug 26 06:13:18 UTC 2010


The comment of class MCMUpdater is currently

<citation>
MCMcmUpdater provides utility methods for updating Monticello packages
from Monticello configurations.

When Monticello configurations are stored in a repository,
MCMcmUpdater acts as an update stream. It first ensures that each
configuration map has been loaded in sequence, then updates the last
configuration map to the most recent version for each specified
package, and finally loads these versions to produce a fully updated
configuration.
</citation>


This class went through a small though important change (see
discussion in this thread). It  should inform people who have not
followed it.

In addition I'd like to have the class comment to give more details so
that a non-specialist in version control / update mechanism issues can
understand it.

My two questions:

1) Is it correct to say that MCMUpdater  handles each Monticello
package so-to-say as having its own update stream? I mean the
succession of Monticello mcz files?

2) Which object is meant here by 'configuration map'?


I'd like to add to the comment.

<proposalForAddition>
MCMUpdater maintains in the variable 'SkipPackages' list of packages
it no longer updates because they have been unloaded for example by
Smalltalk unloadAllKnownPackages.
</proposalForAddition>


And we need a description of the class variables

DefaultUpdateURL
LastUpdateMap
SkipPackages
UpdateMissingPackages

And I'd like to have more.

Could somebody help please?

--Hannes



On 8/25/10, Chris Cunningham <cunningham.cb at gmail.com> wrote:
> Oh, and for anyone trying this, you will need to load the
> MonticelloConfigurations before Monticello changes.
>
>



More information about the Squeak-dev mailing list