Stef, I definitely intend to keep supporting Metacello on ALL platforms ... I have not made any public changes to Metacello since the summer (roughly) so in one sense I've been ignoring all platforms equally for a while now ... I am looking forward to porting the Metacello Scripting API work to Pharo2.0, but I have a number of balls in the air at them moment ...
From reading subsequent emails, it sounds as though the bar is a lot lower than it was before ... it sounds like it won't be as big a job to get things running on Pharo2.0 as I anticipated, but I still need to find some time just to get my development environment (FileTree, git/github, travisCI) operational on Pharo2.0 ...
Dale ----- Original Message ----- | From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> | To: Pharo-project@lists.gforge.inria.fr | Cc: metacello@googlegroups.com | Sent: Wednesday, February 20, 2013 10:14:33 AM | Subject: Re: [Pharo-project] Metacello issues on Pharo 2.0 | | Dale | | We are investing massively on metacello so now this is important for us to | know if you will continue | to maintain it or not. | Because if this is not the case then we will have to rethink our strategy. | | Stef | | | | > Christophe, | > | > I'm not exactly sure what your problem is ... | > | > I have to admit that I haven't kept up with Pharo2.0 since last summer when | > I couldn't use Pharo2.0 for development because of OsProcess issues. I | > know that recently those issues have been cleared up, but I haven't had | > the time to return to Pharo2.0 and check things out (I'm facing more | > issues with getting PHaro2.0 to work with travis-ci, etc. so it will be a | > big undertaking for me to fully support Pharo2.0). | > | > I've got a fairly recent Pharo2.0 image and it looks like there are | > pharo-specific versions for each of the packages loaded into Pharo2.0. I | > assume that the tests are all passing with those versions, although I | > can't say whether or not the tests had to be modified to pass in Pharo2.0 | > as well ... which is likely to be a source of one of the problems you are | > looking at ... | > | > I don't know where the configuration exists that is being used to manage | > the changes for Pharo2.0 and the tests, but that is probably a good | > starting point ... if you are not using the proper Pharo2.0 configuration, | > you won't be getting the proper packages loaded ... | > | > Dale | > ----- Original Message ----- | > | From: "Christophe Demarey" <Christophe.Demarey@inria.fr> | > | To: metacello@googlegroups.com | > | Cc: Pharo-project@lists.gforge.inria.fr | > | Sent: Friday, February 15, 2013 6:09:27 AM | > | Subject: [Pharo-project] Metacello issues on Pharo 2.0 | > | | > | 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' | > | | > | | > | | > | 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): | > | | > | | > | So, it seems there are some problems. Do we use the rigth versions of | > | Metacello packages? | > | | > | Regards, | > | Christophe. | > | | > | | > | | > Chr | > |