Hi. I was thinking about this thread. The described solution works pretty well, but something you should be aware (I think) is that even if it doesn't fail, the generated results could be different than the expected. What I mean is that if you want to load something which at a certain point you do not make explicit WHICH version of a package to load (say you are using #bleedingEdge, or #latestVerison, or you let some defaults for project references or empty version, etc), then Metacello may find a different version in the local directory than the one that exist in the "real/online" repository. To conclude...the resulting image will be always the same only if all versions of all packages are explicitly defined. I am right? Thanks On Thu, Jul 21, 2011 at 6:14 PM, stephane ducasse < stephane.ducasse@gmail.com> wrote:

On Jul 21, 2011, at 5:46 PM, jtuchel wrote:

...

Hi again,

I just wanted to let you know I could solve the problem with Norbert's and Dale' help.

And here is a little writeup of how I did it: http://joachimtuchel.wordpress.com/2011/07/21/pharo-how-to-load-a-metacello-...

Thanks guys!

In the meantime, I am wondering if the idea of having a tool that extracts a complete Configuration from a repo isn't helpful for more scenarios than the one I've mentioned here. In most companies, you have to hand the complete source code of a specific product version into a special version control system, so an extract of a repo that includes a complete ConfigurationOfXXX with all required packages in their specific versions is exactly what's needed for this.

yes ;) And we need that for the distribution repository.

...

Joachim

-- Mariano http://marianopeck.wordpress.com