[p4] Perforce Clients Running on Mac OS where Machine NameChanges

[Jeff Grills]

If you don't want perforce to "help" you out in this case, you can
always set the hostname to nothing (an empty string) in the client.  The
client can then be used from any machine.  Using P4CONFIG is probably a
better solution though.

j 

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of paul goffin
Sent: Thursday, September 20, 2007 4:23 AM
To: Gabor Maghera
Cc: Perforce User
Subject: Re: [p4] Perforce Clients Running on Mac OS where Machine
NameChanges

You can always spoof the hostname with the "-H" switch to all p4
commands
and/or set the hostname in the options within the relevant GUI.
(p4v/p4win).

A P4CONFIG file can also spoof the hostname.

hostname is only there to prevent people accidentally using the same
client
on different physical disks.  It's intended to be easy to override if
you know what you're doing and are doing it deliberately.

Paul.

Quoting Gabor Maghera <gmaghera at gmail.com>:

> Here's the problem:
> Our laptops take on a different host name depending on whether you are
> connected to the LAN directly or via VPN.  Any workspace created in
Perforce
> will not work by default with both configurations, only with the host
name
> used at creation, since that is part of the workspace description.
> Therefore, the user must change the host name set in the  workspace in
order
> to be able to resume work when switching from on- to off-site and vice
> versa.
_______________________________________________