On Tue, 2008-04-01 at 20:43 +0100, Paul Moore wrote: > On 31/03/2008, Paul Moore <[EMAIL PROTECTED]> wrote: > > On 31/03/2008, Steve Borho <[EMAIL PROTECTED]> wrote: > > > > > > On Mon, 2008-03-31 at 22:55 +0100, Paul Moore wrote: > > > > > > Can someone enlighten me on what TortoiseHg does to get a working > > > > convert/subversion extension? > > > > > > The subversion python bindings are included in the library.zip file that > > > comes with the installer. The easiest way to do this is to have the > > > bindings installed on the machine that generates the installer (py2exe > > > picks them up and adds them to library.zip). It's near impossible to do > > > this after the fact. > > > > Hmm, I thought I'd tried this. Maybe not. I'll give it another go and > > try to work out what I did wrong. If that is the case, possibly the > > build instructions should make that clear (it's one thing I did check > > pretty closely, and when I didn't find it, I assumed other magic was > > needed). > > One thing that definitely fails is using the -b 1 flag on python > setup.py py2exe when building the installer. That's part of the > standard build instructions, but the Subversion bindings definitely > crash when used like that. > > If I don't include the -b 1 flag, I get a layout more like TortoiseHg > (with all the DLLs in the same directory as hg.exe) but it still > fails. The results I get are odd, though: > > >hg convert file:///C:/SVN/lua4nt/trunk xyz > *** failed to import extension hgext.hgconfig: No module named hgconfig > *** failed to import extension hgext.qct: No module named qct > initializing destination xyz repository > ** unknown exception encountered, details follow > ** report bug details to http://www.selenic.com/mercurial/bts > ** or [EMAIL PROTECTED] > ** Mercurial Distributed SCM (version ee5313bc3c0c) > Traceback (most recent call last): > File "hg", line 20, in <module> > mercurial.dispatch.run() > File "mercurial\dispatch.pyc", line 20, in run > File "mercurial\dispatch.pyc", line 29, in dispatch > File "mercurial\dispatch.pyc", line 45, in _runcatch > File "mercurial\dispatch.pyc", line 364, in _dispatch > File "mercurial\dispatch.pyc", line 417, in _runcommand > File "mercurial\dispatch.pyc", line 373, in checkargs > File "mercurial\dispatch.pyc", line 358, in <lambda> > File "hgext\convert\__init__.pyc", line 127, in convert > File "hgext\convert\convcmd.pyc", line 335, in convert > File "hgext\convert\convcmd.pyc", line 50, in convertsource > File "hgext\convert\subversion.pyc", line 217, in __init__ > File "hgext\convert\subversion.pyc", line 486, in latest > File "hgext\convert\subversion.pyc", line 119, in __iter__ > EOFError > > Where did hgconfig and qct come from? They aren't in my mercurial.ini, > so I don't see what enabled them. I do have TortoiseHg installed, but > not on my PATH.
TortoiseHg must set a registry item that specifies the HGRC path to it's installed Mercurial.ini. So long as TortoiseHg is installed, all Mercurial commands will use it's INI file. > Also, I'm not sure why I get that EOFError. I don't with a > python-based hg or with TortoiseHg. This, I don't know about. -- Steve Borho ([EMAIL PROTECTED]) http://www.borho.org/~steve/steve.asc Key fingerprint = 2D08 E7CF B624 624C DE1F E2E4 B0C2 5292 F2C6 2C8C ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
