Call for testing: hackable Mercurial for Windows

Angel Ezquerra angel.ezquerra at
Thu Oct 20 18:06:28 CDT 2011

On Fri, Oct 21, 2011 at 1:00 AM, Adrian Buehlmann <adrian at> wrote:
> On 2011-10-20 22:56, Angel Ezquerra wrote:
>> On Wed, Oct 19, 2011 at 3:31 AM, Matt Mackall <mpm at> wrote:
>>> In an effort to get more Windows people hacking on Mercurial, I've built
>>> a proof-of-concept package here:
>>> (~50MB)
>>> that contains:
>>> - private copy of Python 2.6.6 (32-bit)
>>> - complete Mercurial history
>>> - pre-compiled extensions (32-bit MinGW gcc 4.6.1)
>>> - hg.exe wrapper to add to your path
>>> - in-place editable source checked out and ready to go
>>> You should be able to unzip this into a directory and start hacking on
>>> Mercurial immediately without affecting your existing Python or
>>> Mercurial installations. Because it contains the actual Mercurial repo,
>>> you should also be able to immediately pull and update to the latest
>>> development versions (until the extensions need recompiling).
>>> Please give it a spin!
>> I gave this a try and it works great! This will make hacking on
>> mercurial so much easier for us windows users!
> Just don't try hacking on thg with that (you, as a thg contributor).
> And make sure your new hg.exe in the PATH doesn't interfere with the
> hg.exe installed by the TortoiseHg binary installer.

That is true that that may get tricky. My system was already quite a
mess with 3 mercurial installations before this one: The one in
c:\python26, the one installed by the mercurial installer and the one
I got by cloning the mercurial repository!

Shouldn't it be possible to just set the HGPATH variable to point to
Matt's package? Shouldn't TortoiseHg, even if run from sources use it
then? (this is me still trying to avoid installing the Visual Studio,
etc, etc :P)


More information about the Mercurial-devel mailing list