Thanks a **lot**. On Jul 4, 2009, at 9:20 AM, Pavel Krivanek wrote:
Finished... see http://code.google.com/p/pharo/issues/detail?id=59
so, some comments:
This patch must be done in *three* separate updates - the first one loads the ChangesOrganizer class. This class contains class variables from the ChangeSorter and class-side methods for changes management. As the postinstallation step the attached code must be evaluated. It switches the class variables dictionary from ChangeSorter to ChangesOrganizer - the second update will load the second changeset. This changeset switches the usages of ChangeSorter to ChangesOrganizer in methods that use it for general changes manipulation. - as the final step the latest changeset removes all class variables from the ChangeSorter and modifies some methods to delegate its functionality to ChangesOrganizer. We step must be done in time when no other class uses the ChangeSorter for changes management. It can break the update otherwise.
I hope that this quite radical update will not end with the headache...
Cheers, -- Pavel
On Fri, Jul 3, 2009 at 9:41 PM, stephane ducasse <stephane.ducasse@free.fr
wrote: Thanks this is a really fast answer :)
I'm cleaning the _ ;) Stef
On Jul 3, 2009, at 9:35 PM, Pavel Krivanek wrote:
Hi Stef,
I'll prepare and upload the updated version for latest Pharo tomorrow. Look at some other issue for now.
Cheers, -- Pavel
On Fri, Jul 3, 2009 at 9:29 PM, stephane ducasse <stephane.ducasse@free.fr
wrote: Hi pavel
I'm trying to understand what I should do for integrating this fix but this is not clear to me. http://code.google.com/p/pharo/issues/detail?id=59
could you help me?
Stef