CVSROOT/nval-tags and cvs lstags

[Alexey M. <al...@hs...>]

Hello,

here is what I've done:

new administrative file is introduced in repository:
CVSROOT/nval-tags.  It is analogous to CVSROOT/val-tags, only it
contains much more information about tags.

This text file contains lines of the following simple format:

BBRANCH_NAME PARENT_BRANCH username timestamp
TTAG_NAME PARENT_BRANCH username timestamp

(adding the "V"-lines, for vendor branches, is being considered).


The 'cvs rtag' subcommand is enhanced so that the server updates this
file with each new tag or branch created in the repository.


cvs lstags
-----------

The new 'cvs lstags' subcommand simply transfers this file to the
client verbatim.  The primary users of this subcommand are various
web-based repository interface a-la viewcvs.cgi.  They get the ability
to display more accurate tree of tags and branches, and are able to do
that extremely quickly.


init-nval-tags.pl
------------------

The 'init-nval-tags.pl' script is provided which scans the existing
repository and gathers tag information, using the RCS 'rlog' program.
It then dumps this information using the nval-tags format.  This
script could be used to initialize the repository for using the new
nval-tags.

This script tries to deduce the correct parent of each tag, however
this could only be a guess because of the RCS legacy in CVS.  Also, it
does not (and could not) handle cases where there is a tag and a
branch with the same name in various parts of repository (it simply
takes the first which it stumbles upon, ignoring others).


legacy
-------

The CVSROOT/val-tags is still handled.  However, it is expected that
the support for this file will be dumped.

--alexm