Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>To answer my own question, the answer appears to be no.</p> <p>I've done some more digging and been in contact with the original author - Frank Kingswood - and the solution is to ensure your depot imports without errors in the first place. Once that's done, Perfarce works an absolute treat.</p> <p>The original abort of the import was down to my usage. After following various instructions found elsewhere - including Stack Overflow - I was trying to use hg clone's destination parameter to get the right repo name. But it looks like the success of the import is sensitive to an interaction between the Perforce client spec root and the destination folder given as this final argument to hg clone.</p> <p><strong>Basically, make sure these folders do not overlap.</strong></p> <p>Depending on the files in Perforce, it <em>may</em> work if you have an overlap, but you could be setting yourself up for a whole heap of trouble in the future.</p> <p>The recommendation is to keep the folders separate. My problem was that I did not want to take the default folder name of the hg folder as the Perforce client spec name - which is what it does if you do not supply a destination folder. But, possibly due to a bug, if you do supply the the destination folder then it <em>has</em> to match the client spec root. Because of this behaviour, I had assumed that the folders actually had to be the same.</p> <p>In Mercurial it is safe to rename the top level folder after the repo has been created. So if you don't want the name to be dictated by the name of the Perforce client spec, then you can just rename afterwards. That's the approach I took.</p> <p>Hope this helps others trying to dip their toes in the Mercurial waters.</p> <p><strong>Update</strong> Frank has updated the Perfarce extension to better trap this case. Get the latest from the <a href="http://www.kingswood-consulting.co.uk/hg/perfarce" rel="nofollow">Perfarce repository</a>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload