[Pharo-project] renggli mirror created on smalltalkhub
dhenrich at vmware.com
Wed Jul 4 11:44:47 EDT 2012
As Stef and Sven have pointed out, the support for git and github is not quite there ... I provide details of what is in my other post.
The basic idea is that Metacello will make it possible for an orderly migration of projects to git/github.
The real advantage of github is not as a mirror site, but as the primary project hosting site ... Here are a couple of the very cool collaborative features of Github:
- per project issue list
- here's a pull request discussion with line by line
annotations of the code diff
- here's the continuous integration history for the metacello project a
build is launched by TravisCI on each "push" to the repository. For the
master branch of the Metacello project I build against both pharo and squeak.
the build loads and runs the unit tests. If the unit tests fail, I get a summary
of the failed tests.
----- Original Message -----
| From: "Herby Vojčík" <herby at mailbox.sk>
| To: Pharo-project at lists.gforge.inria.fr
| Sent: Wednesday, July 4, 2012 5:39:38 AM
| Subject: Re: [Pharo-project] renggli mirror created on smalltalkhub
| Camillo Bruni wrote:
| > On 2012-07-04, at 14:02, Sven Van Caekenberghe wrote:
| >> On 04 Jul 2012, at 13:50, phil at highoctane.be wrote:
| >>> I am using Mercurial for all of the other projects and
| >>> technologies.
| >>> With a full copy of everything locally, it helps indeed when we
| >>> get crashes...
| >>> But GIT/Hg isn't giving you the change sorter.
| >> I have used/tried FileTree/Git(hub) a bit and it is cool and it
| >> works.
| >> But I do miss (tools) integration in the image.
| >> The workflow also changes a bit, it is no longer all Smalltalk.
| >> IMHO it is not yet quite ready.
| > indeed. I remember that my solution didn't change a thing from the
| > image side
| > experience. It was "simply" a git backend for MC.
| But, well, you should then do something with near-zero obstacle
| experience, like mirroring all included-by-default packages on github
| butbucket, uploading your wrapper/backend with ConfigurationOf and
| bells and whistles into some MC repository (SmalltalkHub?), include
| it the code that automatically re-assigns repository paths from
| SqueakSource/whatever into github, so people can just load it and get
| That way, more or them could actually try.
More information about the Pharo-dev