.\"
.\"	aegis - project change supervisor
.\"	Copyright (C) 1991-1995, 1998, 2001 Peter Miller;
.\"	All rights reserved.
.\"
.\"	This program is free software; you can redistribute it and/or modify
.\"	it under the terms of the GNU General Public License as published by
.\"	the Free Software Foundation; either version 2 of the License, or
.\"	(at your option) any later version.
.\"
.\"	This program is distributed in the hope that it will be useful,
.\"	but WITHOUT ANY WARRANTY; without even the implied warranty of
.\"	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
.\"	GNU General Public License for more details.
.\"
.\"	You should have received a copy of the GNU General Public License
.\"	along with this program; if not, write to the Free Software
.\"	Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111, USA.
.\"
.\" MANIFEST: User Guide, The History Tool, Using SCCS
.\"
.bp
.nh 2 "Using SCCS"
.LP
The entries for the commands are listed below.
SCCS uses a slightly different model than Aegis wants,
so some maneuvering is required.
The command strings in this section assume that the SCCS command
\fIsccs\fP
is in the command search PATH,
but you may like to hard-wire the path,
or set PATH at the start of each command.
(It is also possible that you need to say ``delta'' instead of ``sccs delta''.
if this is the case, these command need to be in the path.)
You should also note that the strings are always handed to
the Bourne shell to be executed,
and are set to exit with an error immediately a sub-command fails.
.LP
One further assumption is that the \fIae-sccs-put\fP(1) command, which is
distributed with Aegis, is in the command search path.  This insultaes
some of the weirdness the SCCS carries on with, and make sht eommands
below comprehensible.
.nh 3 "history_create_command"
.LP
This command is used to create a new project history.
The command is always executed as the project owner.
.LP
The following substitutions are available:
.IP ${Input}
absolute path of the source file
.IP ${History}
absolute path of the history file
.LP
The entry in the
.I "config"
file looks like this:
.E(
history_create_command =
  "ae-sccs-put \e
    -y$version -G$input \e
    ${d $h}/s.${b $h}";
.E)
.LP
It is important that
the \fIhistory_\%create_\%command\fP and
the \fIhistory_\%put_\%command\fP be the same.
This is necessary for branching to work correctly.
.nh 3 "history_get_command"
.LP
This command is used to get a specific edit back from history.
The command may be executed by developers.
.LP
The following substitutions are available:
.IP ${History}
absolute path of the history file
.IP ${Edit}
edit number, as given by history_\%query_\%command
.IP ${Output}
absolute path of the destination file
.LP
The entry in the
.I "config"
file looks like this:
.E(
history_get_command =
  "get -r'$e' -s -p -k \e
    ${d $h}/s.${b $h} > $o";
.E)
.nh 3 "history_put_command"
.LP
This command is used to add a new "top-most" entry to the
history file.
This command is always executed as the project owner.
.LP
The following substitutions are available:
.IP ${Input}
absolute path of source file
.IP ${History}
absolute path of history file
.LP
The entry in the
.I "config"
file looks like this:
.E(
history_put_command =
  "ae-sccs-pit \e
    -y$version -G$input \e
    ${d $h}/s.${b $h}";
.E)
.LP
Note that the SCCS file is left in the \fInot-edit\fP state,
and that the source file is left in the baseline.
.LP
It is important that
the \fIhistory_\%create_\%command\fP and
the \fIhistory_\%put_\%command\fP be the same.
This is necessary for branching to work correctly.
.nh 3 "history_query_command"
.LP
This command is used to query what the history mechanism calls the top-most
edit of a history file.
The result may be any arbitrary string,
it need not be anything like a number,
just so long as it uniquely identifies the edit
for use by the
.I history_get_command
at a later date.
The edit number is to be printed on the standard output.
This command may be executed by developers.
.LP
The following substitutions are available:
.IP ${History}
absolute path of the history file
.LP
The entry in the
.I "config"
file looks like this:
.E(
history_query_command =
  "get -t -g ${d $h}/s.${b $h}";
.E)
.LP
Note that "get" reports the edit number on stdout.
.nh 3 "Templates"
.LP
The
.I lib/config.example/sccs
file in the Aegis distribution
contains all of the above commands,
so that you may readily insert them into your project
.I config
file.
.LP
Also, there are some subtleties to writing the commands, which are not
present in the above examples.  In particular, being able to support file
names which contain characters which are special to the shell requires
the use of the ${quote} substitution around all of the files names in
the commands.
.LP
In addition, it is possible to have a much more useful description for
the \fB\-y\fP option.  For example: ``\f[CW]-y${quote ($version) ${change
description}}\fP'' inserts the version number and the brief description
into the file's log.  This means that using the \fIsccs prs\fP(1) command
will provide quite useful summaries.
.nh 3 "Binary Files"
SCCS is unable to cope with binary files.  However, Aegis
will transparently encode all such files, if you leave the
\fIhistory_\%content_\%limitation\fP field unset.