[Rant] Shrinking problems and rampant interdependencies

Bob Arning arning at charm.net
Tue Jul 24 12:26:21 UTC 2001


On Tue, 24 Jul 2001 08:09:48 -0400 Kevin Fisher <kgf at golden.net> wrote:
>> BTW, a common reason for large images are change sets - dumping all the
>> updates can bring you a long step forward.
>
>How do I dump the updates?  My shrinkForIpaq method is essentially
>a copy of majorShrink with some key changes (ie dump MVC, keep anything
>that breaks Morphic if removed).   If majorShrink abandons the updates
>then it's probable that my shrinkForIpaq does as well.

Kevin,

	ChangeSorter classPool at: #AllChangeSets 
		put: (OrderedCollection with: Smalltalk changes).

is in the current #majorShrink.

Cheers,
Bob




More information about the Squeak-dev mailing list