[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Symbolic tag information after a 'cvs release'

From: Greg A. Woods
Subject: Re: Symbolic tag information after a 'cvs release'
Date: Mon, 8 Apr 2002 02:52:03 -0400 (EDT)

[ On Monday, April 8, 2002 at 13:18:24 (+1000), Sonam Chauhan wrote: ]
> Subject: Re: Symbolic  tag information after a 'cvs release'
> Hmm, all we want is to have the symbolic tag of the CVS version released, to 
> be 
> stored in a file on the release server. This is so that deployment 
> verification 
> can be automated across a cluster.
> Have you heard of a CVS variable ( called, say, "$tag$" ? :) that holds the 
> tag, 
> if any, assigned to the the main branch.

Ah, I see now what you're asking for.

Once you've tagged your release, you should create a copy of it with the
"cvs export" command, probably with the '-kv' option (in addition to, of
course, the '-r RELEASE-TAG' option).

Then anywhere in your files that the RCS keyword "$Name$" appears, it
will be replaced by the value of the tag.

See the node 'export' (titled "export--Export sources from CVS, similar
to checkout") in the CVS manual.

Note this keyword only works from "cvs export", and it does not work for
sticky (eg. branch) tags in normal working directories.  It would be
nice to have a "$Branch$" keyword that would be magic to CVS and be
expanded to the branch tag name if a sticky branch tag is in effect in
the working directory where the file is located, but nobody's
implemented one that I know of yet.

                                                                Greg A. Woods

+1 416 218-0098;  <address@hidden>;  <address@hidden>;  <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]