I've spent less time using locks on a ConfigurationOf, but the
original lock implementation was intended to allow you to have
your own disk-based repository for ConfigurationOfs and
BaselineOfs ... If I'm not mistaken, I think you will want to use
a mcz repostiroy (MCDirectoryRepository) for your local repo, The
filetree repo will only store one version of each mcz file and
with a configuration (especially if you don't lock the version)
you could very easily be attempting to load different versions of
the same package ...
The lock command associates the version/repository with another
repository, but does not map package versions[1].
The BaselineOf lock and filetree work well together, because the
BaselineOf does not specify package versions ...
Dale
[1]https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUserGuide.md#locking
On 9/3/16 3:27 PM, Sean DeNigris wrote:
Does #lock work for
Configurations the same way I understand it for
baselines? In other words, if one
evaluated:
Metacello new
configuration: 'Sample';
repository:
'filetree://<fulll-path-to-directory>;
lock.
Would that load the packages from
filetree://<fulll-path-to-directory>, as
well as the config?
--
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.
--
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
