.TH "CvsGraph" "1" "1.4.0" "B. Stultiens" "CVS/RCS Utilties"
cvsgraph \- A CVS/RCS repository grapher
\fBcvsgraph\fR [\fIoptions\fR] [\fIfile\fR]
\fBCvsGraph\fR generates images and imagemaps from CVS/RCS repository files.
Add a branch box at the end of the trunk too. This option negates the
\fBbranch_dupbox\fR setting from the configuration file.
Read alternate config from \fIfile\fR.
Enable debug mode at \fIlevel\fR. The amount of information is determined by a
bitwise or of the following: 1=config lexer, 2=config parser, 4=rcsfile lexer,
8=rcsfile parser, 16=rcsfile structure. The \fIlevel\fR argument may be in
decimal, octal or hexadecimal format.
A brief description of possible options.
Generate an imagemap instead of an image.
Also write an imagemap to \fIfile\fR. This can be usefull if you want to
generate both image and imagemap simultaneously. This halves the total time
spent on accessing the repository file because it is parsed only once.
However, keeping track of auto-generated files can be a bit of a hack if
used in http requests (unless you pass both image and html-file in one
Note 1: most time is used for the image-drawing routines (actually libgd),
so you might want to think twice in CGI apps.
Note 2: you can still use '\fB-o\fR' to specify an output file for the image.
And, if you also specify '\fB-i\fR', then you'll get two imagemaps, for
whatever purpose that might be.
Try to reduce the image size by adjusting inter\-revision spacing and moving
trunks more left. This options negates the \fBauto_stretch\fR setting from the
Use \fIname\fR as imagemap name (has only effect in combination with
\&'\fB\-i\fR'). This option overrides \fBmap_name\fR in the configuration file.
Use \fImod\fR as cvsmodule.
This option overrides \fBcvsmodule\fR in the configuration file.
Set \fIcfg_option\fR to \fIvalue\fR. Multiple \fB-O\fR are allowed as well
as multiple options can be set simultaneously by separating them with ';'.
See \fBcvsgraph.conf(5)\fR for a detailed list of options.
See also \fBCONFIGURATION\fR below.
Output to \fIfile\fR. Otherwise, output is written to standard output.
Be quiet (i.e. no warnings)
Use \fIpath\fR as cvsroot.
This option overrides \fBcvsroot\fR in the configuration file.
Strip all untagged revisions from the tree. Only the first, last and each
tagged revision of each trunk will be shown. This will greatly reduce the size
of the generated image if you didn't tag everything (and are not interested in
all revisions). This option negates the \fBstrip_untagged\fR setting from the
Also strip the first revision in a branch if untagged and not a branchpoint.
This has only effect if \fBstrip_untagged\fR or option '\fB\-s\fR' is set.
The '\fB\-S\fR' option negates the \fBstrip_first_rev\fR from the configuration
Draw the tree upside down (newest revision at the top). This option negates the
\fBupside_down\fR setting from the configuration file.
Print version and exit.
Set the HTML level of compliance for image maps. Use \fI3\fR for HTML 3.x,
\fI4\fR for HTML 4.x and \fIx\fR for XHTML. Default is HTML 3.x compatibility.
Use \fItxt\fR for expansion
\fBCvsGraph\fR starts with reading a configuration file. If the '\fB\-c\fR'
option is given on the commandline, then it is read. Otherwise, \fBcvsgraph\fR
first looks for a configuration file in the current directory using
\fI./cvsgraph.conf\fR and, if not found, tries to open
\fI/usr/local/etc/cvsgraph.conf\fR. Defaults and commandline overrides
will be used if no configuration file can be opened. The format of the
configuration file is described in \fBcvsgraph.conf(5)\fR. Configuration
parameters entered on the commandline have always precedence over the
configuration file. Configuration options are processed in the following
- configuration file
- '\fB-O\fR' commandline options
- other commandline overrides (\fB-bkMmrSsu\fR)
If you do not want to process any configurationfile, then you can set option
\'\fB-c /dev/null\fR', which will read an empty configuration file.
The location of a repository file is determined by the configuration parameters
\fBcvsroot\fR and \fBcvsmodule\fR and the respective commandline options
\&'\fB\-r\fR' and '\fB\-m\fR'. The \fBcvsroot\fR, \fBcvsmodule\fR and \fIfile\fR
are concatenated with separating '/' path\-separators forming the final
No path\-separator is appended if \fBcvsroot\fR and \fBcvsmodule\fR are empty
strings. An error message is issued if the resulting path cannot be opend.
Note that \fBcvsgraph\fR does not atempt to check any validity of the path
components. This enables a user to open any file on the file\-system by setting
\fBcvsroot\fR and \fBcvsmodule\fR to empty strings.
For example, \fIcvsgraph \-r '' \-m '' ../myfile,v\fR would try to open the
file \fI../myfile,v\fR. Note that a variety of possibilities yield the same
file and all have their advantages and drawbacks, which are mostly related to
the possible use of the parameters in text expansions.
If no \fIfile\fR is given on the commandline, then input is read from standard
input. This can make expansion strings somewhat strange looking, but they are
composed with the information available. If no input file was given, then the
input filename for expansion is set to \fB<stdin>\fR.
The output generated by \fBcvsgraph\fR can be either an image (default) or and
HTML imagemap ('\fB\-i\fR' and '\fB-I\fR' options).
Images can have several formats, depending on the capabilities of the gd
library on which the drawing is built. The configuration allows for GIF, PNG or
JPEG type images. Newer versions of gd do no longer support GIF and PNG will be
Generation of imagemaps conforms to the HTML standard and maps rectangular
regions of the image where revisions and branches are drawn. Additionally, an
extra rectangular region is generated between revisions to support diff
Configuration file read for default layout parameters.
\fBCvsGraph\fR is written and maintained by B. Stultiens.
Send comments and bugreports to \fIcvsgraph@akhphd.au.dk\fR and
visit the homepage at:
.SH "SEE ALSO"