On 11.05.2010, at 02:41, commits@source.squeak.org wrote:
David T. Lewis uploaded a new version of MonticelloConfigurations to project The Trunk: http://source.squeak.org/trunk/MonticelloConfigurations-dtl.76.mcz
- An MCConfiguration specifies the configuration of a set of related Monticello packages. It maintains an ordered list of package versions and a list of repositories in which the packages may be found. The package versions are treated as minimum version levels for each specified package.
That's not quite right. A configuration always loads exactly the versions that are listed in it. But a configuration can be instructed to "update itself" to the highest-numbered ones from a repository. After that, those can be loaded.
Thats what happens when you choose "update from repositories" in MCConfigurationBrowser - it only changes the version numbers but does not install them yet.
That happens automatically using MCMcmUpdater, so there the two-step process is not obvious. But it still is essential to work - it first loads all the update maps, and after the last one is loaded, it updates that one from the repository, and installs its versions.
- Bert -
On Mon, May 10, 2010 at 07:57:07PM -0700, Bert Freudenberg wrote:
On 11.05.2010, at 02:41, commits@source.squeak.org wrote:
David T. Lewis uploaded a new version of MonticelloConfigurations to project The Trunk: http://source.squeak.org/trunk/MonticelloConfigurations-dtl.76.mcz
- An MCConfiguration specifies the configuration of a set of related Monticello packages. It maintains an ordered list of package versions and a list of repositories in which the packages may be found. The package versions are treated as minimum version levels for each specified package.
That's not quite right. A configuration always loads exactly the versions that are listed in it. But a configuration can be instructed to "update itself" to the highest-numbered ones from a repository. After that, those can be loaded.
Thats what happens when you choose "update from repositories" in MCConfigurationBrowser - it only changes the version numbers but does not install them yet.
That happens automatically using MCMcmUpdater, so there the two-step process is not obvious. But it still is essential to work - it first loads all the update maps, and after the last one is loaded, it updates that one from the repository, and installs its versions.
Thanks Bert.
Phew, writing comments is not as easy as it looks ;-)
I just posted an update that might be slightly less incorrect.
Dave
On 10.05.2010, at 20:40, David T. Lewis wrote:
On Mon, May 10, 2010 at 07:57:07PM -0700, Bert Freudenberg wrote:
On 11.05.2010, at 02:41, commits@source.squeak.org wrote:
David T. Lewis uploaded a new version of MonticelloConfigurations to project The Trunk: http://source.squeak.org/trunk/MonticelloConfigurations-dtl.76.mcz
- An MCConfiguration specifies the configuration of a set of related Monticello packages. It maintains an ordered list of package versions and a list of repositories in which the packages may be found. The package versions are treated as minimum version levels for each specified package.
That's not quite right. A configuration always loads exactly the versions that are listed in it. But a configuration can be instructed to "update itself" to the highest-numbered ones from a repository. After that, those can be loaded.
Thats what happens when you choose "update from repositories" in MCConfigurationBrowser - it only changes the version numbers but does not install them yet.
That happens automatically using MCMcmUpdater, so there the two-step process is not obvious. But it still is essential to work - it first loads all the update maps, and after the last one is loaded, it updates that one from the repository, and installs its versions.
Thanks Bert.
Phew, writing comments is not as easy as it looks ;-)
I just posted an update that might be slightly less incorrect.
Dave
Looks good to me. Thanks! Now the next time someone wonders, they have at least a bit of documentation :)
- Bert -
squeak-dev@lists.squeakfoundation.org