[p4] Question about headTime.
jgrills at drivensnow.org
Wed Apr 5 16:10:57 PDT 2006
Why don't you just one perforce client dedicated for this purpose, issue a
p4 sync against it, and then if any files come down, start a build? That
way you let Perforce do what it is supposed to do - send you only the files
that have changed. That seems -so- much easier.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Kevin Regan
Sent: Wednesday, April 05, 2006 3:42 PM
To: Kevin Regan; Jeff With The Big Yellow Suit
Cc: perforce-user at perforce.com
Subject: Re: [p4] Question about headTime.
To be a bit more specific, the script is looking at the headTime of each
file that was used to build a local RPM. If the headTime is later than the
timestamp on the local RPM (which is not checked in to Perforce), then the
script does a "p4 sync". Unfortunately, there is no way to tell how the
headTime relates to the timestamp on the local RPM because the headTime is
(possibly) based on the clock from some other user's machine.
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user