Le 10/09/2015 20:29, Alexandre Bergel a écrit :
But, all well considered, relying only on the underlying vcs for
versions, but writing chunk files, could it work? With the
gitfiletree framework, all version / meta information is external
to the source files, so Metacello could use that and have
everything it needs. Would someone be interested by that?
Are you suggesting to have a different format, which could be .mcs that
is like .mcz but without all the metadata?
That would be that. The mcs would be the chunk format that Pharo and all
Smalltalks have (i.e. fileouts).
This means that we will need
another UI since Monticello will not work.
No, it would simply be another type of repository for Monticello. I have
already done the work for GitFileTree (recreate a MC-like API even if
the metadata comes from git instead of the mcz), and you would reuse that.
It would be totally transparent to you. Metacello, Gofer, Configurations
would work.
Can you estimate the amount of work to do?
I'd start from GitFileTree, isolate the git commands and the MC API and
copy them to the new repository type, add a chunk reader over a zip
archive, and add the chunk writer. I'd reuse the GitFileTree repository
inspector because it is already designed for that.
For someone who knows a bit the internals of a MC repository, it
wouldn't take long.
Shouldn't forget to have a good chunk of tests cases and sample
repositories: filetree would be my reference there.
Thierry
Alexandre
