.ig
 Copyright (C) 1993,1994 by the author(s).
 
 This software is published in the hope that it will be useful, but
 WITHOUT ANY WARRANTY for any part of this software to work correctly
 or as described in the manuals. See the ShapeTools Public License
 for details.

 Permission is granted to use, copy, modify, or distribute any part of
 this software but only under the conditions described in the ShapeTools 
 Public License. A copy of this license is supposed to have been given
 to you along with ShapeTools in a file named LICENSE. Among other
 things, this copyright notice and the Public License must be
 preserved on all copies.


Author: Andreas Lampen (Andreas.Lampen@cs.tu-berlin.de)

$Header: shape_patch.1[6.0] Fri Jun 25 17:01:45 1993 andy@cs.tu-berlin.de frozen $
..
.TH "SHAPE_PATCH" 1 "" \n(dy.\n(mo.\n(yr
.SH NAME
shape_patch \- shapeTools RMS generate patch file
.SH SYNOPSIS
\fBshape\ patch\ OLDRELEASE=<name1>\ NEWRELEASE=<name2>\ [PATCHFILE=<filename>]
.sp
.SH DESCRIPTION
\fIShape patch\fP generates a patch file for updating
\fI$(OLDRELEASE)\fP to \fI$(NEWRELEASE)\fP. Both releases are 
identified by release names associated with the macros OLD-/NEWRELEASE
on the command line. Valid release names are those generated by any
of the shape_RMS (pre-)release building procedures (see
shape_releas(1)). Performing 'vl -all' with the release
identification file as argument usually gives a good overview of
existing release names.
Patch generation happens recursively over all subsystems being part of
the current node. Hence, triggering \fIshape patch\fP from the top
node of the central source repository creates a patch file for the
whole system.
.PP
The output of shape patch is stored in a file
named \fI<name1>+2+<name2>.pat\fP. When the PATCHFILE macro is set on
the command line, $(PATCHFILE) is taken as output file name instead.
Defining PATCHFILE=\- on the command line causes the patch to be
written to standard output.
\fBNote:\fP For patches invoking multiple subsystems, $(PATCHFILE)
should be set to an absolute pathname. If not, the patch generation
procedure will leave an equally named patch file for each visited
subsystem.
.PP
The patch is constructed using the \fIvdiff(1)\fP command and can
be applied to any installation of $(OLDRELEASE) by invoking
\fIpatch(1)\fP.
.SH INCONVENIENCES
On System V machines, the generated patch file name will almost
certainly exceed the 14 characters filename length limit.
.SH SEE ALSO
shape_releas(1), vdiff(1), patch(1)
.SH FILES
<name1>+2+<name2>.pat