[p4] RCS keywords

Mike mikee at mikee.ath.cx
Thu Nov 9 10:59:09 PST 2006

On Thu, 09 Nov 2006, Ivey, William might have said:

> > -----Original Message-----
> > From: perforce-user-bounces at perforce.com
> > [mailto:perforce-user-bounces at perforce.com]On Behalf Of David Alban
> > 
> > I'm curious if the folks on this list choose to use perforce's
> > capability of expanding these keywords, or whether you have other
> > methods of determining which version of a controlled file is in
> > production.  Or, when you want to know, do you always go back to the
> > repository and get a checksum of the head (or other relevant) 
> > version of
> > the file to compare with that of the file in production.
> We do use it for some human-readable files that will be distributed
> outside our development environment. Script files mostly. For most
> source files it makes no sense, and for others our build number
> system contains enough information to determine the revisions of the
> files and this number is added during the build process.

I have not used perforce enough yet to have an opinion about this
with respect to perforce, however with rcs and cvs I found having the
expanded (oh, and sccs too) ident marks in source code extremely
important in that it allows you to use 'ident BINARY' to verify
all headers and support files in a binary are the same version
and that there is not a build issue. For sccs use 'what BINARY' (I
think, it's been a long time for sccs).


More information about the perforce-user mailing list