This is prcs.info, produced by makeinfo version 4.0 from prcs.texi.

   This file describes PRCS, the Project Revision Control System.

   Copyright (C) 1994, 1996, 1997 by Paul N. Hilfinger.  All rights
reserved.

   We distribute PRCS under the terms of the GNU General Public
License, Version 2, which we have included with this release in the
file named `COPYING', and in the "Copying" section of this manual.  As
indicated in the License, we provide the program "as is" without
warranty of any kind, either expressed or implied, without even the
implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

INFO-DIR-SECTION Version Control
START-INFO-DIR-ENTRY
* PRCS: (prcs).           The Project Revision Control System.
END-INFO-DIR-ENTRY


File: prcs.info,  Node: Recursive Keyword Replacement,  Next: Formatted Keyword Instances,  Prev: Recognized Keywords,  Up: Keywords

Recognized Keywords
===================

   Keyword replacement is recursive.

   Replacement of a keyword takes place on a string which is either the
quoted contents of a `Format' keyword or the defined value of a regular
keyword instance.  When this string contains an instance of a keyword
which is not currently being replaced, it recursively outputs the value
of that keyword.  Processed text is not reexamined.  A keyword instance
is not replaced when it is appears during a recursive replacement of
the same keyword, to prevent loops.

   One minor glitch in the above description.  Since the `$' character
delimits keyword instances, tt is necessary to prevent `$' characters
from being inserted as the value of a non-formatted keyword.  All text
after the first `$' would otherwise end up being inserted into the
document.  For example, if the keyword K had value "I have a `$'
character!" were replaced:

     $K: I have a $ character!$

   Then, the next replacement would result in:

     $K: I have a $ character!$ character!$

   and so on.  Therefore, when spurious `$' characters are found inside
the contents of a regular keyword value (not `Format'), they are
replaced with the `|' character.


File: prcs.info,  Node: Formatted Keyword Instances,  Next: Keywords and File Identifiers,  Prev: Recursive Keyword Replacement,  Up: Keywords

Formatted Keyword Instances
===========================

   Sometimes, you want keyword replacement data to appear without the
leading `$keyword:' and trailing `$'.  A formatted keyword instance
allows this.  An appearance in your file of

     $Format: "STRING"$
     STRING

will cause `prcs checkin' to replace the next line of the source file
(i.e., the line after the second `$') with STRING, after first making
modified keyword substitutions in it.  Specifically, each instance of
`$KEYWORD$' in STRING (for which KEYWORD is one of the recognized
keywords) is replaced by just the data that would be placed to the
right of the `:' in a simple keyword instance.  The `Format' instance
itself is not altered--only the subsequent line.  For example, if a
file in a project contains

     /* $Format: "static char* version = \"$ProjectVersion$\";"$ */
     static char* version = "x.x";

then the version of the file checked in for version 1.2 of the project
will contain

     /* $Format: "static char* version = \"$ProjectVersion$\";"$ */
     static char* version = "1.2";

   The format string may not contain newlines.  It may contain quotation
marks if they are stropped with a backslash, as in the example above.
In general, the backslash quotes the succeeding character.  Any keyword
instances on a list after a `Format' instance are ignored (that is,
they are left unchanged by keyword substitution).  Any nested instance
of `Format' is also left unchanged.


File: prcs.info,  Node: Keywords and File Identifiers,  Prev: Formatted Keyword Instances,  Up: Keywords

Keywords and File Identifiers
=============================

   The actual content of a working file upon checkout depends on two
things: the  internal file identifier recorded for it and the contents
of the project descriptor.  The internal file identifier designates a
particular "raw" file contents stored in the repository that never
changes once it is first created.  The checked out file consists of this
contents modified by keyword replacement. If the same file identifier is
used for two files in two different projects, the checked-out working
files will differ in the values supplied for these keywords.  This is a
subtle point, but it is significant when you copy a file identifier from
one project to another.

   For example, suppose that file F in version 1.2 of project P
contains the line

     /* $ProjectVersion: 1.2$ */

and that its entry in the Files attribute of P.prj is

         (F (P/0_F 1.1))

If you decide to rename F to G for the next version of P, you can do so
by changing its line in the Files attribute to

         (G (P/0_F 1.1))

When you check the project back in, creating version 1.3, this same
line will be retained as its file identifier (assuming, that is, you
made no changes to G or its former incarnation, F).  However, in
version 1.3 of P, G  will contain

     /* $ProjectVersion: 1.3$ */

   That is, PRCS actually performs all keyword replacement on check-out
(think of it as lazy replacement).  It only makes a user-visible
difference in the handling of internal identifiers.  It also has a
considerable effect on the performance of partial checkins (those that
contain a list of specific files and directories to check in, and copy
all unmentioned files from file identifiers listed in the Files
attribute). Because PRCS does not have to examine the files excluded
from the file list for keywords, it can process them very quickly.


File: prcs.info,  Node: Subprojects,  Next: Importing Project Versions,  Prev: Keywords,  Up: Top

Subprojects
***********

   You can use PRCS to "bundle together" a set of projects (so that
they may be released together, for example).  Suppose that P is the name
you want to give to the (new) combined project, with P1, P2, and P3 the
names of the subprojects.  To create the initial version of P, take the
following steps.

  1. Go into a directory that is to serve as the working directory for
     P.

  2. Use prcs checkout to create a `.prj' file for P.

  3. For each subproject, Pi, create a subdirectory Pi, and in that
     subdirectory, execute the command
          % prcs checkout -r... Pi Pi.prj
     (replacing `...' with the appropriate version specifier).  This
     checks out the `.prj' file for Pi into Pi.

  4. Modify the Files entry for P to list the `.prj' files for the Pi.

  5. Check in P.

   To create a working copy of this version of P (including working
copies of all its subprojects' files), use the following (Bourne shell)
commands (I'll assume that 0.1 is the version name for P).

     $ prcs checkout -r0.1 P
     $ for i in P1 P2 P3; do
     >   (cd $i; prcs checkout $i)
     > done

Obvious modifications of this procedure will serve to create updated
versions of P.

   With a little care, we can automate this process a bit further.
Suppose that we establish a convention that we tag each subproject
descriptor file in the Files list of P:

     (Files
       ...
       (P1 (...) :tag=project)
       (P2 (...) :tag=project)
       (P3 (...) :tag=project)
       ...
     )

This allows a general-purpose version of the checkout procedure above,
one that does not require that we remember the names of all the
subprojects:

     % prcs execute -r0.1 --match :tag=project P -- prcs checkout {}


File: prcs.info,  Node: Importing Project Versions,  Next: Environment Variables,  Prev: Subprojects,  Up: Top

Importing Project Versions
**************************

   PRCS allows you to create a sequence of project versions out of a
sequence of releases of a source directory tree.  You may want to do
this, for example, if you are installing successive versions of some
system imported from elsewhere and wish to be able to retrieve old
versions, while still saving space by storing only the changes between
successive versions.  (See *Note package and unpackage::, if you want
to move or copy an entire project from one repository to another.)

Tracking imported versions
--------------------------

   The process is simple.  For concreteness, let us use the name `P' as
the project name.  For the first imported version, we create `P' and
populate it with the first version of the imported source files.  In
the directory that contains the imported files, use the commands

     % prcs checkout P
     % prcs populate P
     # Edit P.prj #
     % prcs checkin P

The editing of `P.prj' might consist of setting the
`Project-Description' and `New-Version-Log' attributes, and possibly
adding `:no-keywords' options to some files.

   When you receive a new release of `P', place it in a directory
structure and, at the top directory of that structure, use the commands

     % prcs checkout P P.prj
     % prcs populate -d P
     # Edit P.prj #
     % prcs checkin P

With the `-d' option, the `prcs populate' command will add any new
files found in the working directory, but not listed in `P.prj', and
will remove any files listed in `P.prj', but not present in the working
directory.  Again, you will probably want to edit the `New-Version-Log'
attribute.

   Imported software sources often have their own version designations,
and you may want to have the PRCS major version identifiers include all
or part of these designations.  Suppose the first such imported release
is called `1.0-beta'.  In the working directory containing this release,
you might type

     % prcs checkout -r1.0-beta.0 P
     % prcs populate P
     # Edit P.prj #
     % prcs checkin P

On receiving a new release from outside, say `1.1-beta', you would put
it under a working directory and, from that directory, issue the
commands

     % prcs checkout -r1.0-beta. P P.prj
     % prcs populate -d P
     # Edit P.prj #
     % prcs checkin -r1.1-beta. P

Keeping parallel local versions
-------------------------------

   Sometimes, you will have local modifications or enhancements to a
piece of imported software, and want to bring your local version up to
date with successive parallel releases of the imported software.  To do
this, use the procedure above for keeping the imported releases.  Put
your own local releases in another major version, let's say `Local'.
To start with, you'll use the initial imported release:

     % prcs checkout -rV P P.prj
     # Edit the project #
     % prcs checkin -rLocal P.prj

Here, V is whatever PRCS version number you have assigned to the
vendor's (the imported) version.  Continue making your local
modifications in major revision `Local'.  When a new external release
comes in, first   make sure the most recent version of your local
version is checked in.  Then put the new imported version into a fresh
directory structure, populate a project file, and check it in as
outlined above.  For concreteness, let's say that your most recent
local version is designated Local.5, and the newly-checked-in imported
version is designated Vendor.3.

   In the working directory for Vendor.3 (which you have just checked
in), issue the command

     % prcs merge -rLocal.@ -n P

to see where the discrepancies are (or use `prcs diff'), and use

     % prcs merge -rLocal.@ P

to merge in the revisions since the last external release with the local
changes since the last release.  Edit the files to resolve conflicts,
and edit `P.prj' as usual. Finally, check the result back in with

     % prcs checkin -rLocal P

which will create version Local.6.  Its parent versions are Local.5 and
Vendor.3.  Alternatively, you could check out the local version,
Local.5, and merge against the vendor branch

     % prcs merge -rVendor.@ P

and checkin as Local.6.  The resulting parent versions are the same in
either case, with the sense of all the merge operations reversed.

Handling renaming
-----------------

   Sometimes, you will find it desirable to rename the files you import
and re-arrange their directory structure in your local version.  You
probably only want to perform this restructuring on the Local branch of
the project, not the Vendor branch.  Initially, you will create your
first local version like this:

     % prcs checkout -rV P P.prj
     # Rename files #
     # Edit P.prj to change the names in the Files attribute so
     # as to correspond to your renaming.
     % prcs checkin -rLocal P.prj

   Editing `P.prj' here consists simply in changing the file names, not
the internal file identifiers.  For example, if the file
`doc/mogrify.1' in branch V is to be called `man/mogrify2.1' in the
Local branch, you would rename the file:

     % mkdir man
     % mv doc/mogrify.1 man/mogrify2.1

   and then you would edit the line for `doc/mogrify.1' in `P.prj',
which might read

       (doc/mogrify.1 (P/0_foobar.1 1.1 644))

originally, into

       (man/mogrify2.1 (P/0_foobar.1 1.1 644))

The internal file identifier, therefore, records the correspondence
between `doc/mogrify.1' in the V branch and `man/mogrify2.1' in the
Local branch.  When either of these files is updated and checked in,
its new internal file identifier will be in the same internal-file
family; thus the correspondence between the files is not lost.

   The concept of an internal-file family (*note Files attribute::) was
introduced to allow `prcs diff' and `prcs merge' to "do the right
things" (that is, compare or merge against the appropriate files) even
in the face of such restructuring.  For example, when comparing a Local
version to a Vendor version, `prcs diff' will compare `doc/mogrify.1'
from the Vendor version with `man/mogrify.1' in the working files of
your Local version.


File: prcs.info,  Node: Environment Variables,  Next: Copying,  Prev: Importing Project Versions,  Up: Top

Environment Variables
*********************

   Certain information that PRCS needs is not likely to be the same for
different users and installations, and is inconvenient or inappropriate
to specify with every command.  In such cases, PRCS takes the
information from environment variables, where they are defined, and
uses some implementation-defined default otherwise.  PRCS checks first
the users's environment, then the builder's compile-time environment,
and finally uses the documented default.  Here is a listing of the
environment variables that PRCS queries, and their meanings.  Run `prcs
config' to see a listing of all the environment variables PRCS is aware
of and their values.

 - Environment Variable: PRCS_CONFLICT_EDITOR
     The path of an editor to run on all merged files that generate
     conflicts immediately after the conflict is produced.  This lets
     you handle conflicts one at a time instead of waiting until a
     merge has completed.

 - Environment Variable: PRCS_DIFF_COMMAND
     Like PRCS_MERGE_COMMAND, a command to produce differences when
     running prcs diff.  There are at least 4 arguments: from label,
     from filename, to label, to filename, preceded by any diff options
     supplied either on the command line or with the PRCS_DIFF_OPTIONS
     environment variable.  See PRCS_MERGE_COMMAND below for an example.

 - Environment Variable: PRCS_DIFF_OPTIONS
     If set, this environment variable supplies space-separated
     arguments for diff.  When diff options are supplied on the command
     line, this variable is ignored.

 - Environment Variable: PRCS_JOB_NUMBER
     If set, this environment variable specifies a default value for
     the job number when the `-j' option is not specified.

 - Environment Variable: PRCS_LOGQUERY
     When defined, query user at checkin for a New-Version-Log, if one
     is missing from the project file.  *Note Version-Log and
     New-Version-Log attributes::.

 - Environment Variable: PRCS_MERGE_COMMAND
     The path of a command to run on files to merge. The command is
     called with 7 arguments: working label, working filename, common
     label, common filename, selected label, selected filename, and the
     output filename.  The command is expected to merge the files and
     place the output in the output filename, which will also be the
     name of the working file.  If there is no common ancestor, the
     file `/dev/null' is used.  To get the default behavior, you could
     use the script performing the following:

          diff3 -maE -Lworkinglabel working -Lcommonlabel common \
            -Lselectedlabel selected > output

     The return value is interpreted as with `diff3' (*note
     (diff)Top::).  Return 0 to indicate no conflicts, 1 to indicate
     conflicts, and 2 to indicate trouble.  _Warning: as the result of
     a symlink, output and working files may be the same!  So, the above
     command will sometimes result in an exploding file because gdiff
     overwrites itself as it merges._


 - Environment Variable: PRCS_PLAIN_FORMAT
     Has the same effect as specifying `--plain-format' on the command
     line.

 - Environment Variable: PRCS_REPOSITORY
     Path to the repository. Defaults to `$HOME/PRCS'.  *Note
     Repository::.

 - Environment Variable: RCS_PATH
     A colon-separated list of additional directory paths in which to
     search for utility programs, including those that are part of RCS,
     the Revision Control System.  The current implementation of PRCS
     uses RCS to implement part of its functions (although in general,
     this fact is transparent to the user).  Since there is no
     universally standard place to install RCS, its location is one of
     PRCS's configuration parameters.  Any utilities that PRCS cannot
     find in the `RCS_PATH' directories it looks for in an
     installation-specific place.

 - Environment Variable: TMPDIR
     If set, this environment variable is used for temporary file
     storage.


File: prcs.info,  Node: Copying,  Prev: Environment Variables,  Up: Top

GNU General Public License
**************************

                         Version 2, June 1991

     Copyright (C) 1989, 1991 Free Software Foundation, Inc.
     675 Mass Ave, Cambridge, MA 02139, USA
     
     Everyone is permitted to copy and distribute verbatim copies
     of this license document, but changing it is not allowed.

Preamble
========

   The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users.  This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it.  (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.)  You can apply it to
your programs, too.

   When we speak of free software, we are referring to freedom, not
price.  Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it in
new free programs; and that you know you can do these things.

   To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

   For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have.  You must make sure that they, too, receive or can get the
source code.  And you must show them these terms so they know their
rights.

   We protect your rights with two steps: (1) copyright the software,
and (2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

   Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software.  If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

   Finally, any free program is threatened constantly by software
patents.  We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary.  To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

   The precise terms and conditions for copying, distribution and
modification follow.

    TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License applies to any program or other work which contains a
     notice placed by the copyright holder saying it may be distributed
     under the terms of this General Public License.  The "Program",
     below, refers to any such program or work, and a "work based on
     the Program" means either the Program or any derivative work under
     copyright law: that is to say, a work containing the Program or a
     portion of it, either verbatim or with modifications and/or
     translated into another language.  (Hereinafter, translation is
     included without limitation in the term "modification".)  Each
     licensee is addressed as "you".

     Activities other than copying, distribution and modification are
     not covered by this License; they are outside its scope.  The act
     of running the Program is not restricted, and the output from the
     Program is covered only if its contents constitute a work based on
     the Program (independent of having been made by running the
     Program).  Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's
     source code as you receive it, in any medium, provided that you
     conspicuously and appropriately publish on each copy an appropriate
     copyright notice and disclaimer of warranty; keep intact all the
     notices that refer to this License and to the absence of any
     warranty; and give any other recipients of the Program a copy of
     this License along with the Program.

     You may charge a fee for the physical act of transferring a copy,
     and you may at your option offer warranty protection in exchange
     for a fee.

  2. You may modify your copy or copies of the Program or any portion
     of it, thus forming a work based on the Program, and copy and
     distribute such modifications or work under the terms of Section 1
     above, provided that you also meet all of these conditions:

       a. You must cause the modified files to carry prominent notices
          stating that you changed the files and the date of any change.

       b. You must cause any work that you distribute or publish, that
          in whole or in part contains or is derived from the Program
          or any part thereof, to be licensed as a whole at no charge
          to all third parties under the terms of this License.

       c. If the modified program normally reads commands interactively
          when run, you must cause it, when started running for such
          interactive use in the most ordinary way, to print or display
          an announcement including an appropriate copyright notice and
          a notice that there is no warranty (or else, saying that you
          provide a warranty) and that users may redistribute the
          program under these conditions, and telling the user how to
          view a copy of this License.  (Exception: if the Program
          itself is interactive but does not normally print such an
          announcement, your work based on the Program is not required
          to print an announcement.)

     These requirements apply to the modified work as a whole.  If
     identifiable sections of that work are not derived from the
     Program, and can be reasonably considered independent and separate
     works in themselves, then this License, and its terms, do not
     apply to those sections when you distribute them as separate
     works.  But when you distribute the same sections as part of a
     whole which is a work based on the Program, the distribution of
     the whole must be on the terms of this License, whose permissions
     for other licensees extend to the entire whole, and thus to each
     and every part regardless of who wrote it.

     Thus, it is not the intent of this section to claim rights or
     contest your rights to work written entirely by you; rather, the
     intent is to exercise the right to control the distribution of
     derivative or collective works based on the Program.

     In addition, mere aggregation of another work not based on the
     Program with the Program (or with a work based on the Program) on
     a volume of a storage or distribution medium does not bring the
     other work under the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,
     under Section 2) in object code or executable form under the terms
     of Sections 1 and 2 above provided that you also do one of the
     following:

       a. Accompany it with the complete corresponding machine-readable
          source code, which must be distributed under the terms of
          Sections 1 and 2 above on a medium customarily used for
          software interchange; or,

       b. Accompany it with a written offer, valid for at least three
          years, to give any third party, for a charge no more than your
          cost of physically performing source distribution, a complete
          machine-readable copy of the corresponding source code, to be
          distributed under the terms of Sections 1 and 2 above on a
          medium customarily used for software interchange; or,

       c. Accompany it with the information you received as to the offer
          to distribute corresponding source code.  (This alternative is
          allowed only for noncommercial distribution and only if you
          received the program in object code or executable form with
          such an offer, in accord with Subsection b above.)

     The source code for a work means the preferred form of the work for
     making modifications to it.  For an executable work, complete
     source code means all the source code for all modules it contains,
     plus any associated interface definition files, plus the scripts
     used to control compilation and installation of the executable.
     However, as a special exception, the source code distributed need
     not include anything that is normally distributed (in either
     source or binary form) with the major components (compiler,
     kernel, and so on) of the operating system on which the executable
     runs, unless that component itself accompanies the executable.

     If distribution of executable or object code is made by offering
     access to copy from a designated place, then offering equivalent
     access to copy the source code from the same place counts as
     distribution of the source code, even though third parties are not
     compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program
     except as expressly provided under this License.  Any attempt
     otherwise to copy, modify, sublicense or distribute the Program is
     void, and will automatically terminate your rights under this
     License.  However, parties who have received copies, or rights,
     from you under this License will not have their licenses
     terminated so long as such parties remain in full compliance.

  5. You are not required to accept this License, since you have not
     signed it.  However, nothing else grants you permission to modify
     or distribute the Program or its derivative works.  These actions
     are prohibited by law if you do not accept this License.
     Therefore, by modifying or distributing the Program (or any work
     based on the Program), you indicate your acceptance of this
     License to do so, and all its terms and conditions for copying,
     distributing or modifying the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the
     Program), the recipient automatically receives a license from the
     original licensor to copy, distribute or modify the Program
     subject to these terms and conditions.  You may not impose any
     further restrictions on the recipients' exercise of the rights
     granted herein.  You are not responsible for enforcing compliance
     by third parties to this License.

  7. If, as a consequence of a court judgment or allegation of patent
     infringement or for any other reason (not limited to patent
     issues), conditions are imposed on you (whether by court order,
     agreement or otherwise) that contradict the conditions of this
     License, they do not excuse you from the conditions of this
     License.  If you cannot distribute so as to satisfy simultaneously
     your obligations under this License and any other pertinent
     obligations, then as a consequence you may not distribute the
     Program at all.  For example, if a patent license would not permit
     royalty-free redistribution of the Program by all those who
     receive copies directly or indirectly through you, then the only
     way you could satisfy both it and this License would be to refrain
     entirely from distribution of the Program.

     If any portion of this section is held invalid or unenforceable
     under any particular circumstance, the balance of the section is
     intended to apply and the section as a whole is intended to apply
     in other circumstances.

     It is not the purpose of this section to induce you to infringe any
     patents or other property right claims or to contest validity of
     any such claims; this section has the sole purpose of protecting
     the integrity of the free software distribution system, which is
     implemented by public license practices.  Many people have made
     generous contributions to the wide range of software distributed
     through that system in reliance on consistent application of that
     system; it is up to the author/donor to decide if he or she is
     willing to distribute software through any other system and a
     licensee cannot impose that choice.

     This section is intended to make thoroughly clear what is believed
     to be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in
     certain countries either by patents or by copyrighted interfaces,
     the original copyright holder who places the Program under this
     License may add an explicit geographical distribution limitation
     excluding those countries, so that distribution is permitted only
     in or among countries not thus excluded.  In such case, this
     License incorporates the limitation as if written in the body of
     this License.

  9. The Free Software Foundation may publish revised and/or new
     versions of the General Public License from time to time.  Such
     new versions will be similar in spirit to the present version, but
     may differ in detail to address new problems or concerns.

     Each version is given a distinguishing version number.  If the
     Program specifies a version number of this License which applies
     to it and "any later version", you have the option of following
     the terms and conditions either of that version or of any later
     version published by the Free Software Foundation.  If the Program
     does not specify a version number of this License, you may choose
     any version ever published by the Free Software Foundation.

 10. If you wish to incorporate parts of the Program into other free
     programs whose distribution conditions are different, write to the
     author to ask for permission.  For software which is copyrighted
     by the Free Software Foundation, write to the Free Software
     Foundation; we sometimes make exceptions for this.  Our decision
     will be guided by the two goals of preserving the free status of
     all derivatives of our free software and of promoting the sharing
     and reuse of software generally.

                                NO WARRANTY

 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
     WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
     LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
     HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
     WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT
     NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
     FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE
     QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
     PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
     SERVICING, REPAIR OR CORRECTION.

 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
     WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
     MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE
     LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
     INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
     INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
     DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU
     OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY
     OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
     ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

                      END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs
=============================================

   If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

   To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

     ONE LINE TO GIVE THE PROGRAM'S NAME AND AN IDEA OF WHAT IT DOES.
     Copyright (C) 19YY  NAME OF AUTHOR
     
     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., 675 Mass Ave, Cambridge, MA 02139, USA.

   Also add information on how to contact you by electronic and paper
mail.

   If the program is interactive, make it output a short notice like
this when it starts in an interactive mode:

     Gnomovision version 69, Copyright (C) 19YY NAME OF AUTHOR
     Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
     type `show w'.  This is free software, and you are welcome
     to redistribute it under certain conditions; type `show c'
     for details.

   The hypothetical commands `show w' and `show c' should show the
appropriate parts of the General Public License.  Of course, the
commands you use may be called something other than `show w' and `show
c'; they could even be mouse-clicks or menu items--whatever suits your
program.

   You should also get your employer (if you work as a programmer) or
your school, if any, to sign a "copyright disclaimer" for the program,
if necessary.  Here is a sample; alter the names:

     Yoyodyne, Inc., hereby disclaims all copyright
     interest in the program `Gnomovision'
     (which makes passes at compilers) written
     by James Hacker.
     
     SIGNATURE OF TY COON, 1 April 1989
     Ty Coon, President of Vice

   This General Public License does not permit incorporating your
program into proprietary programs.  If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library.  If this is what you want to do, use the
GNU Library General Public License instead of this License.


