On 30.01.2008 21:09, Steve Borho wrote: > On Wed, 2008-01-30 at 20:49 +0100, Adrian Buehlmann wrote: >> Am I correct in assuming that I should have a "qct.py" or "qct.exe", >> "qct.bat" >> or "qct.cmd" somewhere in an install directory? But there is no such file >> under >> "C:\Python25" and neither under "C:\Program Files\TortoiseHg". > > No, qct is only launched via the Mercurial extension. > >> If I do a search for files and directories containing "qct" in their name >> inside >> "C:\Python25" I get: >> >> C:\Python25\share\qct\ >> C:\Python25\Lib\site-packages\qct-1.5-py2.5.egg-info\ >> C:\Python25\Lib\site-packages\qctlib\ >> C:\Python25\share\qct\qct.1.html > > You're missing this file: > C:\Python25\lib\site-packages\hgext\qct.py
Exactly! (see below) >> (3 directories and a html file) >> >> Inside "C:\Program Files\TortoiseHg" there is a archive file "library.zip" >> which >> contains a folder "hgext" which has a file "qct.pyc" (but no "qct.py"). >> >> I also tried renaming the directory "C:\Program Files\TortoiseHg" so that its >> content is no longer accessible from the path, but that didn't help either. > > No, tortoisehg sets registry key values that newer Mercurial versions > look for and older ones don't. It's stupidly complex right now until a > new NSI installer is released. > >> My folder "C:\Python25\Lib\site-packages\hgext" does not contain a >> "qct.py" >> (shouldn't it?). A dir of that folder gives: > > That's the crux of the problem. Qct didn't install correctly. You're > fighting through three layers of badness: > > 1) NSI and TortoiseHg really don't play well together > 2) PyQt didn't install correctly at first > 3) Qct was broken by #2. > > I think it can be resolved by removing Qct then re-installing it from this URL > (though it may still be on your hard-drive). > > http://qct.sourceforge.net/qct-1.5.win32-py2.5.msi > That did the trick! Thanks a lot! Now I have a leading-edge "hgtk log" (synced from http://tortoisehg.sourceforge.net/hg/tortoisehg-dev -- beware, I might start hacking there...:-), a "hgtk commit" using the qct-dialog and the context menus from TortoiseHG for production-use all at the same time (plus a Python source Mercurial available for tweaking). <side note> I've renamed "hg.exe" in "C:\Python25\Scripts" to "hg2.exe" and "hg-script.py" to "hg2-script.py". So I have now the official TortoiseHG "hg" from "C:\Program Files\TortoiseHg" and the Python sources based hg2 "hg" from "C:\Python25\Scripts" (ready for potential tweaking...): > hg version Mercurial Distributed SCM (version 02884e56c217+win32extras) ... > hg2 version Mercurial Distributed SCM (version 0.9.5) ... </side note> Thanks a lot for your help and apologies for my weird, unusal setup. --Adrian ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
