Metacello is perfectly well maintained, and runs on a number of Smalltalks.
I do not know. If Dale did not had a look since this summer this is 8 months ago. I have no problem that this would happen. I just want to know because we want to build all the validation of packages on top of metacello.
It broke on Pharo 2.0 because things changed too quickly, too quickly for Dale to keep up.
Probably. But I do not think so.
What would be vastly more constructive than implying that Dale has abandoned Metacello would be applying some Pharo effort towards making it work again on 2.0.
Frank I spent a lot of time pushing Metacello, christophe is working on a tool so that everybody can produce more easily configuration. Now my question is still valid. I just want to know because my time is counted and christophe is trying to understand metacello since some time and we should move forward. Stef
frank
Stef
On Feb 15, 2013, at 3:09 PM, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:
Hi all,
I have issues with Metacello on Pharo 2.0
If I load and run tests for the version used in Pharo1.4, it gives: (ConfigurationOfMetacello project version: '1.0-beta.31.1.4') load: 'Tests'
<Capture dâécran 2013-02-15 à 14.45.15.png>
Metacello packages shipped with Pharo 2.0 are all packages derived from the latest stable Metacello baseline (1.0-beta.31.1.5) except the MetacelloToolBox. If I load and run tests packages with version described in the latest stable Metacello baseline (1.0-beta.31.1.5), i.e. :
Metacello-TestsCore-DaleHenrichs.14 and Metacello-TestsMC-dkh.351,
it gives (Pharo 2.0 #20547): <Capture dâécran 2013-02-15 à 14.55.36.png>
So, it seems there are some problems. Do we use the rigth versions of Metacello packages?
Regards, Christophe.