Excellent comment. Thank you cbc!

Hannes

On Thu, 26 Aug 2010 06:54:59.885 0000, commits at source.squeak.org
<commits at source.squeak.org> wrote:
> A new version of MonticelloConfigurations was added to project The Inbox:
> http://source.squeak.org/inbox/MonticelloConfigurations-cbc.82.mcz
>
> ==================== Summary ====================
>
> Name: MonticelloConfigurations-cbc.82
> Author: cbc
> Time: 25 August 2010, 11:54:43.082 pm
> UUID: 8fee1f94-014b-9949-9125-4649684d4c66
> Ancestors: MonticelloConfigurations-cbc.81
>
> Updated comment for MCMcmUpdater to explain the recent changes to this
> class.
>
> =============== Diff against MonticelloConfigurations-cbc.81 ===============
>
> Item was changed:
>   Object subclass: #MCMcmUpdater
>   	instanceVariableNames: ''
>   	classVariableNames: 'DefaultUpdateURL LastUpdateMap SkipPackages
> UpdateMissingPackages'
>   	poolDictionaries: ''
>   	category: 'MonticelloConfigurations'!
>
> + !MCMcmUpdater commentStamp: 'cbc 8/25/2010 23:52' prior: 0!
> - !MCMcmUpdater commentStamp: 'dtl 5/10/2010 23:22' prior: 0!
>   MCMcmUpdater provides utility methods for updating Monticello packages
> from Monticello configurations.
>
> + When Monticello configurations are stored in a repository (or
> repositories), 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.
> +
> + Currently if a set of packages are unloaded from the image, using this
> class to reload them may cause problems, depending on what dependencies
> those classes have.  Success is not assured.
> +
> + If you wish to not have MCMcmUpdater update packages, there are two ways
> to handle this:
> + 1) To not update any packages not currently in the image, evaluate
> + 		MCMcmUpdater updateMissingPackages: false
> + 	Note that any new packages added to the repositories will not be picked
> up when this is turned off.
> + 	To re-enable updating of missing packages disabled in this way, evaluate
> + 		MCMcmUpdater updateMissingPackages: true
> + 2) To not updat specific packages, evaluate
> + 		MCMcmUpdater disableUpdatesOfPackage: <packageName>
> + 	To re-enable updating of a specific package turned of by method 2,
> evaluate:
> + 		MCMcmUpdater enableUpdatesOfPackage: <packageName>
> + 	To re-enable updating of all packages previously disabled by method 2,
> evaluate
> + 		MCMcmUpdator enableUpdatesForAllPackages
> +
> + Note that work is progressing to automatically not update packages that
> are unloaded.  At this time, this is not turned on.
> +
> + Class Variables definitions:
> +
> + DefaultUpdateURL - this is the URL that will be checked by default for
> updates.  This would be set for a common standard location to check.
> +
> + LastUpdateMap - Keeps track of the last configuration map, so that the
> utility will not have to run through the full history in the repositories
> each time you ask to update.
> +
> + SkipPackages - Keeps track of the specific packages that are not to be
> updated in this image (usually because they were unloaded).
> +
> + UpdateMissingPackages - Indicates if this utility should attempt to load
> packages that are not currently in the system.
> + !
> - 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. !
>
>
>