2014-12-04 8:27 GMT+01:00 Max Leske
<maxleske@gmail.com>:
That�s because they should be superseded by the libgit2 bindings.
If I'm not mistaken, they originally were what Ben suggested: a complete git reimplementation in Smalltalk via a FileSystem abstraction layer.
The idea is great and works quite well. There are two problems however and they are the reasons I chose to go with bindings:
- such an implementation is very hard to maintain and the chance of introducing bugs is just off the charts
- performance and memory allocation need a lot of working around (and praying)
The Pharo "whole" export to github would be based on that work, along with that 'almost like FileTree, but not the same' file format.
Not quite. The export simply produces (FileTree) artifacts and writes them to disk. There is no hard dependency to FileSystem-Git (although that might have been the plan at some point).
But correct me if I got that wrong.
Thanks for the reminder (and the hard work you're putting into the libgit2 bindings),
Thank you for your patience :)