[p4] Syncing to USB drive - then changing computers

[Geoff Rowland]

Thanks for all of the suggestions!

 

From: Dave Lewis [mailto:dlewis78731 at gmail.com] 
Sent: Thursday, April 10, 2008 2:43 PM
To: Jeff A. Bowles
Cc: Geoff Rowland; perforce-user at perforce.com
Subject: Re: [p4] Syncing to USB drive - then changing computers

 

Say, couldn't they also use the AltRoot stuff to locate the client
differently for the 2nd machine? Just a thought. 

dave



On Thu, Apr 10, 2008 at 10:13 AM, Jeff A. Bowles <jab at pobox.com> wrote:

Short answer:  yes, you can do it.
Here's the technical part that has to be consistent at every step along
the
way. (Get this right, and the rest is easy.)

The workspace area must be the same drive/pathname, on the same physical
disk, of the same platform type (e.g. Windows or Mac or whatever), to
use
the same workspace name and call it "the same".   (The "same platform"
stuff
really has to do with end-of-line being consistently interpreted on both
machines.)


So...

  1. The user with the removable disk drive on Windows can have
  workspace "joe-portablews", which is a flash-drive that Joe uses for
  development work when at home or at work.  He puts it on the drive J:
and
  the workspace files are in J:\p4filesarea. (Really, it's the D: drive
at
  work and the E: drive at home, but Joe uses drive mapping /
substitution so
  that he can use the same pathname ("J:\p4filesarea") on both machines.
  2. The two people sharing the ancient 1.0 patch area on a network
  fileserver can do the same thing, mapping M:\1.0patcharea to a shared
  workspace called "1.0patches-maintenance" or something like that.
It's
  populated and edited by Windows users only, and everyone maps it to
the M:
  drive (and gets the rest of the path right) before doing any work.
  3. The Linux user whose Perforce workspace directory is
  /home/suzanne/work, although it's actually on a NetApp fileserver and
is a
  shared disk.  It is, still, the same pathname and the same volume, so
  Suzanne can use the workspace from multiple machines.

In each case, the user needs to play a bit with the "Host:" field of the
client workspace spec before starting.

So, probably example #1 is your situation. In general, it's pretty easy.

Remember, "local workspaces never overlap."  (This means
"C:\george\xxx.txt"
is part of a single workspace, or no workspace, but never more than one.
The
database record of what-you-have --- it's in db.have --- gets awfully
upset
when its memory is out-of-sync with reality.)

    -Jeff Bowles


On Thu, Apr 10, 2008 at 6:52 AM, Geoff Rowland <growland at blueomega.com>
wrote:


> I would like to sync files to a removable hard drive, then send that
> hard drive to a remote user (since it would take days for them to sync
> over the internet).  Is it possible for the remote user to login to
> Perforce and have Perforce recognize the date of the files on the
> removable hard drive and only sync files that have been updated
between
> the time the hard drive was synced on site and the time the user
> received it?
>
>
>
> If this is possible, how do I go about doing it? (windows)
>
>
>
> Cheers,
>
> Geoff
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>




--
---
Jeff Bowles - jeff.a.bowles at gmail.com

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user