At 10:55 AM 12/12/2000 +0000, Colin Dunlop wrote:

This model works really well. The real key is to use the same "platform type" for all your Perforce operations - add/edit/submit/resolve/etc for a particular client name. (An example of "platform type" is "Unix", "NT", "Mac", etc.)

The rules I tend to stay with are these: 1. If it's the same pathname to the same disk volume, then you can use the same client name from different machines. For example, if it's a shared disk but everyone gets to it using /home/jab/work, then I use the name "jeff.dev" to get to it from each Unix platform I want, adding/editing/submitting to my heart's content. (The same goes for moving my ZIP disk between work and home: it's the E: drive on both machines, so I can call it "jeff.nt" and move the disk back and forth. If it were not the same drive letter, I might use NT-isms to have an alias - it might be drive J: on both machines as an alias, to allow me to do this trick.) 2. If it's the same platform type (Unix, NT) for all the machines who need to touch it (add/edit/submit) I don't sweat CR-LF issues. If it's different platform types, I try to use different workspaces and use "submit on the first machine, sync to retrieve the updates onto the second machine" to transfer work. That way, I'm not outsmarting Perforce's CR-LF mechanism. 3. On Unix, I try to be careful about symbolic links - in general, I try to make "pwd" output as intuitive as possible, so that "cd X ; pwd" produces a full pathname to "X" instead of some weird symlink expansion. Otherwise, programs that look at the "current working directory's pathname" get confused, and Perforce is no exception. 4. (This next one's a personal choice) I don't share Perforce workspaces between NT and Unix. Ever. It's too easy to edit on NT a file that was sync'ed on Unix, accidently adding \r characters to it, which the next checkin on Unix will treat as new data to the file. I just don't do it - it's too easy to forget and do something I'll regret. 5. (Another personal choice) I never run on an NT machine without the MKS Toolkit. Made this decision 12 years ago, when the above sentence would read "I never run on a DOS...", but it still stands.

-Jeff Bowles