Stef, True. But it also got caught, perhaps because it was where it had no business being. The great thing about configurations and Hudson is that the server will build multiple artifacts. I think among them should be some bloated images for reasons just like this. The core and a leaner dev would also be in the mix.
Bill ________________________________________ From: [email protected] [[email protected]] On Behalf Of Stéphane Ducasse [[email protected]] Sent: Thursday, January 13, 2011 3:27 AM To: [email protected] Subject: Re: [Pharo-project] Dirty MC Packages in Pharo-1.1.1-OneClickCogVM why do you need method wrapper in dev? Again this goes with my mail about pushing metacello dsitributions versus pharo-dev+++ Stef On Jan 12, 2011, at 10:15 PM, Mariano Martinez Peck wrote: > yes, that was a hack I had to do becuase at that moment Cog didn't support > well objects as methods, used by MethodWrappers, and when running its tests, > it crashed. > we wanted to create a quick image so that people could start using cog and > help testing it. > > this is not the case anymore in Pharo 1,2 > > so, if someone wants, the real solution is to create a new one click of 1.1.1 > (without touching by hand method wrappers) and put new CogVMs. > > cheers > > mariano > > On Wed, Jan 12, 2011 at 8:10 PM, Sven Van Caekenberghe <[email protected]> wrote: > Yesterday I downloaded Pharo-1.1.1-OneClickCogVM from > > > https://gforge.inria.fr/frs/download.php/27524/Pharo-1.1.1-OneClickCogVM.zip > > and I noticed it has two dirty MC packages (MethodWrappers and Tests). > > This is probably a glitch, but not nice and confusion for beginners. > > Sven > > >
