Perfarce extension oddity...

[Steve Borho]

On Wed, Jul 21, 2010 at 6:13 PM, Steven Johnson <stejohns at adobe.com> wrote:
> I just found out about the Perfarce extension and have been (excitedly!) trying it out, but I'm getting an odd result, and I can't figure out if the problem is my config, or an intrinsic limitation, or a bug...
>
> I have a client in Perforce that maps something like
>
>        //depot/foo/... //my-machine/perforce-stuff/foo/...
>
> When I sync this using Perforce, my local copy looks something like
>
>        ~/perforce-stuff
>                foo
>                        foo-contents-1
>                        foo-contents-2
>                        foo-contents-3 (etc)
>
> On the other hand if I use Perfarce like so:
>
>        hg clone p4://my.perforce.server:1666/my-foo-client ~/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)
>
> If I set "keep=false" in the Perforce options, I get just a single copy, but still one layer too deep:
>
>        ~/perforce-stuff
>                foo
>                        foo
>                                foo-contents-1
>                                foo-contents-2
>                                foo-contents-3 (etc)
>
> I'm hoping I just misconfigured something, because this oddity will make using Perfarce unnecessarily painful for my usecase.

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/...

-- 
Steve Borho