Dale Henrichs
Dale Henrichs
going from Pharo to VW presents another set of issues ... some of which can be addressed with options (no methodProperties.json file, no monticello.meta directory). The primary issue of types...
Frank, Not quite sure what `tailor` does, but you can do the "conversion" right now by opening a FileTree repository and use the Monticello `copy` command to copy an mcz...
Ah... it would walk the mcz files and copy .. for git you'd want to do that for sets of packages (Metacello configuration files) to get the state of the...
Right but for multi-package projects, the only way to know what package versions work together is to go with the ConfigurationOF... If you create a separate git repository for each...
It has always bugged me that there is no correlation between versions of different mcz packages that are _supposed_ to work together, but then I guess that's why I invented...
The merge scheme does sound like a technique that will allow you to reconstruct the commit history for multiple packages. There is still the issue of _Monticello branches_ ... both...
Frank, The commit history looks very cool! It is very tempting to rebuild the Metacello repository using your script so I can have the early history included as well ...
Oh, I won't be converting Metacello real soon ... probably this fall sometime as I get close to a 1.0 release ... original timestamps would be real cool! I've done...
see also the [Metacello issue](https://github.com/dalehenrich/metacello-work/issues/16)
Let's attempt to address Issue #56 at the same time ...