Max, You have reason to complain...
Not all projects use Metacello so there are still cases where the configuration is only found in the MetacelloRepository. Sometimes developers forget to copy the configurations to the MetacelloRepository. And so on.... In self defense: 1. Use the configuration found in the project repository. 2. Use the configuration found in MetacelloRepository If there are configs in both places and they are not in synch, contact the project maintainers and let them know. If you want to _know_ which config file is later (and whether or not they are even related), you can look at the history for both files and compare UUIDs or find a common ancestor based on UUID. Examining the ancestry of a version is the only way to know how two different mcz relate to one another. If you have two mcz files with a common ancestor, you are still confronted by a dilemma as to which one should you use.... With all that said, I am interested in knowing what was "wrong" with the configurations. Were they two unrelated branches of a configuration or was one configuration way out of date with respect to the other, or??? I'm asking because from a Metacello perspective once a Metacello version is released it should never be changed and that means that for released versions it doesn't matter whether or not you are using the latest configuration, unless the configurations are way out of date. If you are usinga Metacello version that is still under #development then it does matter whether or not you are using the latest configuration. Dale ----- Original Message ----- | From: "Max Leske" <[email protected]> | To: [email protected] | Sent: Tuesday, August 16, 2011 11:59:59 PM | Subject: [Pharo-project] Policy for storing metacello configurations | | I would like to complain a bit about the current way Metacello | configurations are distributed in different repositories. I ended up | using the wrong configuration for two different projects twice in | just two days. Apart from the date in the configuration file (and | possibly the version number, although that's not as reliable) | there's no easy way to tell which configuration is the most recent. | | Some people seem to have adopted MetacelloRepository as the standard | repository for all configurations, others keep the configuration for | a project in the project repositories and a third group uses both | repositories (where one repository contains outdated versions of | course…). | | Can we please agree on a simple policy on where to store the | configuration for a project? I am sure that this would make life | easier for all of us. | | Cheers, | Max |
