Perfarce extension oddity...

[Steven Johnson]

On Jul 21, 2010, at 6:06 PM, Steve Borho wrote:

On Wed, Jul 21, 2010 at 6:13 PM, Steven Johnson <stejohns at adobe.com<mailto:stejohns at adobe.com>> wrote:
I have a client in Perforce that maps something like

       //depot/foo/... //my-machine/perforce-stuff/foo/...

I end up with a duplicate copy, nested an extra layer deep, like so:

       ~/perforce-stuff
               foo
                       foo-contents-1
                       foo-contents-2
                       foo-contents-3 (etc)
                       foo
                               foo-contents-1
                               foo-contents-2
                               foo-contents-3 (etc)


You typically want to create a client spec just for perfarce that maps
the parts you want mirrored in Mercurial to the root.. as in:

//depot/sub/dirs/deep/foo  //myPerfarceClient/foo/...

Tried that: for this custom client spec, I have

    Root = ~/perforce-stuff
    //depot/long/path/tofoo/... //my-machine/foo/...

But I'm still getting the same result. I'll keep poking around (time to peek at perfarce.py, I suppose) -- just not sure if this was "expected" or a known issue, etc...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100722/a9b2260a/attachment.htm>