9 messages in com.perforce.perforce-userWorking at home with an existing client
FromSent OnAttachments
RonO...@illuminate.com05 Feb 1999 08:28 
Scot...@seanet.com05 Feb 1999 09:10 
Davi...@home.chat.net05 Feb 1999 10:27 
Scot...@seanet.com05 Feb 1999 10:58 
Davi...@home.chat.net05 Feb 1999 11:28 
Scot...@seanet.com05 Feb 1999 12:09 
Stev...@qualcomm.com05 Feb 1999 12:37 
Scot...@seanet.com05 Feb 1999 13:09 
Step...@vance.com07 Feb 1999 16:15 
Subject:Working at home with an existing client
From:Step...@vance.com (Step@vance.com)
Date:02/07/1999 04:15:27 PM
List:com.perforce.perforce-user

Ron Olson wrote:

I would appreciate any experiences/solutions for working at home and picking up where you left off with your client from work.

We work with Windows NT and client roots are usually something like c:\src. We use Virtual Private Networking (VPN) to connect from home which essentially puts our home machine on the network. However, the work client will not work since c:\src is on a different machine.

If the user can check everything thing in, she can go home, use a different client, sync everything, and be all set as long as she will be able to check everything in before returning to work.

I tried sharing the folder and using one with a root of \\<host>\<folder> which works from both places, but means over the network (dialup line and modem, thus slow) compiles and for some strange reason adding new files does not work.

Thanks,

Ron Olson

I fully sympathize with your plight. How does one work in a distributed fashion when only things checked in are distributed?

The basic problem is that Perforce only lets you sync from checked in files. On the other hand, your network speed at home is too slow to do full file system sharing. The result is that you want to fake file system sharing, as far as Perforce is concerned.

I suggest that the way to do this in the context of the tool set is to create a branch to contain your work. When you want to work at home, submit all work in progress to the branch and sync from it at home. Do the reverse to send your changes back to work.

Once you're done with the development, throw the branch away. It's only purpose is to synchronize your distributed workspace. It has no place in the version history of the source base. It isn't even required to be consistent in any way at any checked in state.

--- ======================================================================= Stephen Vance | mailto:steve at vance.com | http://www.vance.com =======================================================================

A computer programmer is a machine for turning coffee into programs. --- Paraphrase of the late mathematician Paul Erdo"s