embedded comments ----- Original Message ----- | From: "Christophe Demarey" <[email protected]> | To: [email protected] | Sent: Thursday, February 21, 2013 1:11:49 AM | Subject: Re: [Pharo-project] Metacello issues on Pharo 2.0 | | Hi Dale | | Sure no problem was tired and nervous because Metacello is key for us.
No harm no foul ... we're on the same page and that's what counts! | I'm sitting with christophe to check. | Information that can interest you | | - on the repository of Pharo the Metacello-Core was fixed to handle | FileReference | Now I do not know how you want to manage it for your bootstrap. | | let us know how you want that we proceed. I will have to look at the changes themselves to determine which direction to go ... if the changes are isolated enough I'd be inclined to hide them in MetacelloPlatform ... that's where the platform uglies go ... If the changes are extensive, then I'd consider extracting out a filedirectory[1]/filesystem[2] utilities package (as was done for zinc and filetree). [1] https://github.com/dalehenrich/filetree/tree/pharo2.0/repository/MonticelloFileTree-FileDirectory-Utilities.package [2] https://github.com/dalehenrich/filetree/tree/pharo2.0/repository/MonticelloFileTree-FileSystem-Utilities.package | | - for the tests (not version 10.32 that I cannot load - I will have a look Metacello 1.0-beta.32 is the Metacello Preview version (not yet released anywhere) and porting that version stopped me cold last summer ... OSProcess was the final straw:) | at profStef to make it 2.0 aware I guess that this is that the problem) | runCase refers to SystemNotifier | | we have to check how we control silently the announcement of the new | announcer. | Probably SystemAnnouncer uniqueInstance suspendAllWhile: | | For the Toolbox problem | | Christophe checked the version of '1.0-beta.31.1.5' since this is the latest | stable version | | | spec | package: 'Metacello-Base' with: | 'Metacello-Base-DaleHenrichs.19'; -> | Metacello-Base-MarcusDenker.20 (no difference) | | | package: 'Metacello-Core' with: 'Metacello-Core-dkh.492'; | -> Metacello-Core-MarcusDenker.494 (handle FileSystem This looks fine and it also looks like it can easily be added to the MetacelloPlatform ... | | package: 'Metacello-MC' with: 'Metacello-MC-dkh.664'; | -> Metacello-MC-StephaneDucasse.666 (apparently we remove the | versions accesssor => look really suspicious) Yeah, that looks very suspicious and tests won't pass without that puppy:) | | package: 'Metacello-Reference' with: | 'Metacello-Reference-DaleHenrichs.31'; | package: 'Metacello-Tutorial' with: | 'Metacello-Tutorial-dkh.25'; | package: 'OB-Metacello' with: 'OB-Metacello-dkh.82'; | package: 'Metacello-TestsReference' with: | 'Metacello-TestsReference-DaleHenrichs.17'; | package: 'Metacello-TestsCore' with: | 'Metacello-TestsCore-DaleHenrichs.14'; | package: 'Metacello-TestsMC' with: | 'Metacello-TestsMC-dkh.351'; | package: 'Metacello-TestsTutorial' with: | 'Metacello-TestsTutorial-dkh.33'; | package: 'Metacello-ToolBox' with: | 'Metacello-ToolBox-dkh.130' | -> Metacello-ToolBox-MarcusDenker.135 | | here this is strange because the version of the toolbox in Pharo is | based on 135 134 133 132 131 127 126 .... so should we take another | version of the toolbox? | May be there was a mistake from our side to take a wrong branch. You are on the right branch, Metacello-ToolBox-dkh.130 is okay (it's part of Metacello 1.0-beta.31.1.5) but Metacello-ToolBox-dkh.131 is part of the Preview release. | | In particular neither version of configurationClasses work in pharo | | configurationClasses | "Return a set of the Metacello configuration classes that have been | loaded into the image." | | <apiDocumentation> | ^ MetacelloProjectRegistration configurationClasses This is code is from the preview version and shouldn't be used...yet. | | configurationClasses | "Return a set of the Metacello configuration classes that have been | loaded into the image." | | <apiDocumentation> | self flag: 'more work needed about MetacelloProjectRegistration'. | ^ Array streamContents: [ :s| | SystemNavigation default allClassesDo: [ :cls| | (cls name beginsWith: 'ConfigurationOf') | ifTrue: [ s nextPut: cls ]]] This is the variant that SHOULD work, presumably there is a problem with SystemNavigation? | | | So this means that we do not know what to do but Christophe cannot work on | 2.0 for versioner. | | | | Stef & Christophe | | | > Stef, | > | > AFAIK, this is the first report of any bugs with Metacello since | > September... just saying.... | > | > Dale | > | > ----- Original Message ----- | > | From: "stephane ducasse" <[email protected]> | > | To: [email protected] | > | Sent: Wednesday, February 20, 2013 11:53:28 AM | > | Subject: Re: [Pharo-project] Metacello issues on Pharo 2.0 | > | | > | | > | > 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 | > | >> <[email protected]> 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. | > | >> | > | >> | > | >> | > | > | > | | > | |
