On 16.08.2011, at 17:04, Chris Muller wrote:

>> At the very least this should warn that it's not just going to store a config, but copy versions over, too.
> 
> "Storing a config" should mean, well, Store the Config in a usable
> state - not leave packages missing.  But I suppose what you're saying
> is, you want to have the packages for a Config distributed across
> multiple repositories.
> 
> How about this:  The packages in the config will be auto-copied to the
> repositories in which any version of that package currently resides
> in?  A "smart" copy..

That would make more sense, yes, though I'd still like to see a warning in that case.

- Bert -