[Pharo-users] Pharo + git workflow
Sven Van Caekenberghe
sven at stfx.eu
Tue Jan 26 10:08:02 EST 2016
> On 26 Jan 2016, at 15:59, Dimitris Chloupis <kilon.alios at gmail.com> wrote:
> To be fair my experience with pharo and git have been not always smooth either. I have the VM crashing again and again completely randomly when it was trying to pull SmaCC as dependency for my project Ephestos, had to drop SmaCC and moving my python type parsing at python side.
> But I find it ironic someone using Monticello, trying to equate git with dark ages, you cant get more dark ages than monticello, frankly. No offense to people who made it , its great that is in there but its full of problems and bad designs and cant even begin to be compared with Github and GIT GUI clients. Monticello is according to my personal opinion by far the worst tool of Pharo.
No it is not. It is a version management system that understands our object and code model, a system that we control. Git just manages blobs, text files at best. Dead text.
(This does not mean it is perfect, nor that it cannot improve, nor that we should not improve our git integration.)
> On Tue, Jan 26, 2016 at 4:51 PM Thierry Goubier <thierry.goubier at gmail.com> wrote:
> 2016-01-26 15:11 GMT+01:00 Sean P. DeNigris <sean at clipperadams.com>:
> NorbertHartl wrote
> > - I need to use BaselineOf instead of ConfigurationOf. Thus you cannot use
> > Versionner anymore
> Unfortunately. This is the biggest drag for me after switching all my
> personal projects to git (GitHub for public and BitBucket for private). I
> had gotten spoiled by Versionner and hand-editing MetaC artifacts feels like
> going back to the dark ages :/
> Well, I guess copying the baselines generated by Versionner into a BaselineOf is probably a way to do it.
> View this message in context: http://forum.world.st/Pharo-git-workflow-tp4874067p4874221.html
> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
More information about the Pharo-users