Hi, yes we need to clarify how it should work :) Esteban
On 27 Sep 2015, at 14:08, Thierry Goubier <thierry.goubier@gmail.com> wrote:
Le 27/09/2015 13:58, stepharo a écrit :
Hi guys
I'm totally lost in git/pharo support. The only thing I got is that we do not need metacello versions just baselines.
Yes. Metacello on git delegates branches to a repository url mechanism resolution (and desactivate the cache) so just baselines are needed (with a few restrictions because of the way a baseline can include another baseline).
Makes handling large projects a breeze compared to configurations.
We have fileTree, TreeMerge, gitFileTree + tons of git expressions. Just looking at the discussion between alex and thierry looks totally scary.
;) Far less scary than adding a self halt in RBParser these days.
Do we have one document explaining the situation clearly?
I think my presentation from PharoDays is still up to date. Nothing has changed yet.
I'm still in the dark about libcgit support / plans...
Note that, from the outside, large projects such as Roassal and Moose use a lot of their energy in solving configurations and merge issues which are linked to the type of repository they use. They also require a significant investment in support tools such as Versionner to get things working.
Thierry