El vie, 21-05-2010 a las 09:13 -0700, Sean P. DeNigris escribió:
I created a Squeak/Pharo SSpec, which puts the fork-specific world menu code into a Platform package.
As I work on the config, I came up against Pharo using Object as a subclass, but the Squeak Inbox requiring (because of the browser tool) MetacelloConfiguration.
What would be the best/easiest way to deal with this?
If the configs have to be forked, then Metacello really loses value (i.e. #squeak and #pharo). And, I do a lot of work in both forks, so it would be a shame to pick one to upload to and not share work that has already been done with half the users.
That was one of the problems of the Configuration Package proposed by Andreas. Promotes copy&paste of configurations (bad bad) and in the long term forks and completely rework to create configurations for Squeak and a different (although similar) for Pharo. As you say, it doesn't matter that Metacello is capable of installing cross-platform packages. With independently created configurations for the same packages, is has been stole of its usefulness and is discouraging Pharo users that have developed ConfigurationOfXXX that worked both in Squeak and Pharo in the past.
Thanks. Sean
-- Miguel Cobá http://miguel.leugim.com.mx