[Pharo-project] [Metacello] Did Pharo 2.0 Update #20200 break Metacello bootstrapping?

Camillo Bruni camillobruni at gmail.com
Thu Jul 12 04:10:24 EDT 2012

On 2012-07-12, at 09:52, Henrik Sperre Johansen wrote:

> On 11.07.2012 18:58, Camillo Bruni wrote:
>> 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
> I wrote yesterday:
> "Filtering with the standard collection methods leaves you with an IdentitySet though, so you'd have to either convert it afterwards, change the curtailing code in deliver:to: (which uses Sequenceable protocol). "

actually that's bug I introduced, but the stuff currently failing is still due to double subscriptions of the RPackageOrganizer

> copyAfter: is exactly that protocol, so you'd probably want to re-review the Announcement changes in addition to the fact that RPackage ends up in that code path in the first place.

Indeed my bad :P.

I quickly wrote a decent implementation that does not have to copy around stuff 
in the case of ifCurtailed...

More information about the Pharo-dev mailing list