Am 03.12.2004 um 09:07 schrieb goran.krampe@bluefish.se:
Hi Marcus and all!
Marcus Denker denker@iam.unibe.ch wrote:
One thing we need to do is updating the in-image packages. (e.g. SUnit). We used to add a changset that loads the package via SqueakMap, but this may be no good idea with the Monticello based packages, as the loader for mzc that is used when Monticello is not present is a bit dumb (it does not delete methods...). So what do we do?
Ned proposed a smart solution - take an image, install Monticello, create a new changeset (or perhaps that is done automagically), upgrade the package in question and then save the changeset for inclusion into the update stream. The changeset should then do the "proper" thing.
And thus we don't force Monticello into the Basic image. :) But I wonder for how long we can do this - IMHO Monticello might be due for inclusion in Basic.
Ok, yes, goo idea. I will do that for SUnit.
Question: did the other maintainers of in-image packages re-integrated the m17n changes into the package? e.g SM has seen some small changes in 3.8alpha... (it's nearly impossible to not touch the packages when doing refactorings, as there is no way to tell what is a package and what not).
Marcus