Well Sean, this sounds like a tools issue ...
Metacello does not care where the ConfigurationOf came from. By design
the ConfigurationOf may be loaded from anywhere ...
Since the "home repo" of a project can change from version to version,
I'm not sure that a tool can always guess right as to the home repo of
the ConfigurationOf ...
With git/github repos on top of FileTree, the BaselineOf is always
loaded from the project repo, so this particular problem doesn't exist
when using BaselinOf ...
Dale
On 04/01/2015 05:58 PM, Sean P. DeNigris wrote:
> I'm experiencing a small inconvenience, but I'm not sure from where to attack
> it...
>
> Here's the scenario:
> 1. I load a ConfigurationOfXyz from a non-canonical repo e.g.
> MetaRepoForPharo40
> 2. I edit the config in Versionner
> 3. I try to commit it via Versionner, but the config is associated with
> MetaRepoForPharo40 only and the project's other packages are associated with
> the canonical repo only. Not finding a common location, Kommitter only lists
> the package cache as a commit location.
>
> I'm thinking the config should be associated to both the repo from where it
> was loaded and also the projects main repo. Does that make sense? If so,
> where/when should that get done?
>
>
>
> -----
> Cheers,
> Sean
> --
> View this message in context:
http://forum.world.st/ConfigurationOfXyz-MC-Repository-Group-tp4816811.html> Sent from the Metacello mailing list archive at Nabble.com.
>
--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
For more options, visit
https://groups.google.com/d/optout.
Locked
