Ben and Sean,

After a bit more thought, I believe that it should be okay to make copies, but there does need to be a single primary repository where the correct and latest configuration can be found.

Putting copies of configurations into repositories to make project discovery easier is a good use of copies. Copies are also useful when creating mirror repos....

But one must be able to determine the location of the canonical repository for the configuration.��

If the configuration were always co-located with the packages then it would relatively easy to figure out where to find the newest and 'correctest' configuration.��

The canonical location should ALWAYS be used in project references.

Dale

On Thu, Aug 7, 2014 at 8:30 PM, Ben Coman <btc@openinworld.com> wrote:

Dale Henrichs wrote:

On Thu, Aug 7, 2014 at 9:40 AM, Sean P. DeNigris <sean@clipperadams.com> wrote:

There are two things that have bothered me about our use of Metacello, but I
couldn't explain exactly why until now. These are two guidelines that I
think are important:
1. ConfigurationOfMyProject should live at repoOfMyProject. Any
MetaRepoForXyz should only be a copy of this config
2. Platform-specific config sections are not optional

Makes a lot of sense and I agree.

Dale

I feel similar. Not that I've published any Configurations yet, but looking in from the outside the current process always made me uneasy that is violates my general principle of DON'T MAKE COPIES.

Maybe the MetaRepoForXyz should not contain any ConfigurationOfMyProject at all, but a CatalogOfMyProject (or MetaOfMyProject) which simply points to the ConfigurationOfMyProject in the project repo.��

cheers -ben