Thanks for the explanation, Dale! May be it's obvious and I'm asking stupid questions but then I don't understand how can I specify in my configuration the differences between the versions of the target platform?
2010/3/20 Dale Henrichs <[email protected]>: > George, > > The mcz files containing the Metacello configurations _are_ copied, but the > configuration itself is not modified in the scheme. > > The idea of using different repositories is to indicate which of the many > different projects are _expected_ or _known_ to work in Pharo1.1 or Pharo1.0. > > For GemStone, I have createed a GemSource MetacelloRepository and I have > copied the metacello configurations that I know have been ported to GemStone. > I've done this so that folks can know what is supported. I make sure that all > of the tests run green and that all of the configs in the GemSource > MetacelloRepository can be loaded. > > It does not stop someone from loading a configuration into GemStone that > isn't in the GemSource MetacelloRepository, but if you do and run into > trouble, my answer will probably be that it hasn't been ported yet. > > The same thing can apply to Squeak, but someone would have to step up to > testing/approving metacello configurations that run with the various versions. > > Without this extra step of approval/testing, it's difficult for someone that > doesn't have their finger on the pulse of the latest and greatest happenings > to know what to expect ... > > Dale _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
