[Pharo-project] [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping?
camillobruni at gmail.com
Wed Jul 11 12:58:04 EDT 2012
The problem we face right now are related to RPackage
Somehow the registration mechanism for system events (classes|methods added|removed|modified)
got mixed up.
Eventually this leads to some warnings when removing methods :/
I thought I fixed it this morning but I was wrong :D
On 2012-07-11, at 18:54, Dale Henrichs wrote:
> I was trying to work with Pharo2.0 the other day and ran into weird modified package issues ... Metacello-Base was involved ... I was actually trying to get something else accomplished and don't have time to debug Pharo2.0 issues, since they are not likely to be directly caused by Metacello...
> ----- Original Message -----
> | From: "DeNigris Sean" <sean at clipperadams.com>
> | To: metacello at googlegroups.com, pharo-project at lists.gforge.inria.fr
> | Sent: Wednesday, July 11, 2012 9:47:21 AM
> | Subject: [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping?
> | (Posting to Metacello and Pharo-project lists)
> | Metacello bootstraps in #20199, but not #20200, #20201, or #20202.
> | Try:
> | Gofer new
> | url: 'http://ss3.gemstone.com/ss/Versionner';
> | package: 'ConfigurationOfVersionner';
> | load.
> | (Smalltalk at: #ConfigurationOfVersionner) project development
> | load:#('Core' 'Spec').
> | When the dialog pops up about loading a package with unsaved changes,
> | if you choose merge and keep the current version for all the removed
> | classes and methods, it bootstraps. If you "Load" instead of Merge,
> | it fails with "MessageNotUnderstood: IdentitySet>>copyAfter:"
> | Sean
More information about the Pharo-dev