[PATCH] Fix the path problem on Windows that prevents to run hg from its own repository

[Kevin Smith]

Giuseppe Bilotta wrote:
> On Sun, 03 Jul 2005 03:02:16 -0400, Andrew Thompson wrote:
> 
> 
>>Matt Mackall wrote:
>>
>>>On Sat, Jul 02, 2005 at 02:54:14PM +0200, Giuseppe Bilotta wrote:
>>>
>>>>This also uses the appropriate command (.append() instead of .extend()
>>>>... sorry, I used the wrong version in the other patch ...)
>>>
>>>Ok, still waiting for other Windows folks need to speak up as to
>>>whether this patch is really needed.
>>
>>NOTE: I don't have a 100% clean machine to test on right now.
>>
>>Mercurial is currently able to run properly even when looking at a 
>>repository of Mercurial on my Windows box
>>
>>D:\rootpull>hg version
>>Mercurial version 38d106db75bc
> 
> 
> The question is: is rootpull a *clean* copy of the hg repository,
> without compiled stuff in it?
> 

I don't have a windows box to test on, so I'm trying to understand what 
the actual problem is. I would have thought that the problem would 
happen if the files in the mercurial directory within the current 
directory didn't match those in the installed mercurial directory.

Is the problem when you run hg from a directory that doesn't actually 
contain hg, but which has a mercurial directory, and that mercurial 
directory doesn't match what is installed?

I would like to really understand the current problem before supporting 
or opposing a solution.

Kevin