[IronPython] The elephant in the room: source control for IronPython
s.j.dower at gmail.com
Sat Oct 30 01:46:00 CEST 2010
Are IronPython and the DLR so closely coupled that you *need* the
source for both to work on it? Or can you simply develop/test
IronPython using the DLR in the GAC?
I'd rather have the standard library as a 'default' part of the
IronPython checkout than the DLR, primarily because a binary distro of
the DLR makes more sense.
On Sat, Oct 30, 2010 at 05:54, Tristan Zajonc <tristanz at gmail.com> wrote:
> I've used both hg+bitbucket and git+github. In my experience, there is very
> little difference between hg and git in terms of workflow. I found both to
> be great and the tools are pretty mature across all platforms. I do think
> GitHub is rapidly becoming a killer application for open source projects.
> If you look at the IronRuby repository
> (http://github.com/ironruby/ironruby), there are already 340 watchers and
> 109 forks, which is a non-negligible consideration imho.
> On Fri, Oct 29, 2010 at 8:10 AM, Noah Gift <noah.gift at gmail.com> wrote:
>> On Thu, Oct 28, 2010 at 11:36 PM, Jeff Hardy <jdhardy at gmail.com> wrote:
>>> On Thu, Oct 28, 2010 at 6:31 PM, Miguel de Icaza <miguel at novell.com>
>>> > Moving to Git seems like a no brainer to me: we only have to move
>>> > IronPython
>>> > there. If we were to pick another of the open source source code
>>> > management systems we would be moving both Ruby and Python away.
>>> Where I'm torn is that IronPython is between a rock and a hard place -
>>> on the one hand, I want to work closely with the Mono project (which
>>> would strongly imply using github), but I also want to be in sync with
>>> the Python community (which has largely embraced hg).
>>> Python's separated stdlib will be a Mercurial repo, and if IronPython
>>> were in Hg we could easily pull in the stdlib as a subrepo. However, I
>>> presume the DLR will stay on github, and we'll need to pull that in as
>>> well, which of course would be easier from git.
>>> Damned if we do, damned if we don't. I'm leaning towards Mercurial
>>> because I prefer it, and it seems like many other people do as well. I
>>> know hg can pull from git, but I don't know about the reverse.
>>> > If the concern is the UI for checking code out for Git, there is a
>>> > transparent bridge that exposes the tree to Subversion which has good
>>> > Windows clients.
>>> Tortoise-Git is actually very nice now. I don't think git's Windows
>>> support is really an issue anymore.
>> Haven't tried it, but this looks interesting:
>>> - Jeff
>>> Users mailing list
>>> Users at lists.ironpython.com
>> Users mailing list
>> Users at lists.ironpython.com
> Users mailing list
> Users at lists.ironpython.com
More information about the Ironpython-users