The policy should be - put a configurationOf in your package - publish when you want a copy of it in metacellorepository I will sit with dale sunday because we want the "publish" to copy all the dependent package also in the DistributionMetacelloRepository On Aug 17, 2011, at 8:59 AM, Max Leske wrote:
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