RCS.pdf

(22 KB) Pobierz
The RCS MINI-HOWTO
The RCS MINI−HOWTO
The RCS MINI−HOWTO
Table of Contents
The RCS MINI−HOWTO. ................................................................................................................................1
Robert Kiesling. .......................................................................................................................................1
1. Overview of RCS. ...............................................................................................................................1
2. System requirements.. ..........................................................................................................................1
3. Compiling RCS from Source.. .............................................................................................................1
4. Creating and maintaining archives. .....................................................................................................1
5. ci(1) and co(1). ....................................................................................................................................1
6. Revision histories. ...............................................................................................................................1
7. Including RCS data in working files. ..................................................................................................1
8. RCS and emacs(1) Version Control. ...................................................................................................1
1. Overview of RCS. ...............................................................................................................................1
2. System requirements.. ..........................................................................................................................2
3. Compiling RCS from Source.. .............................................................................................................2
4. Creating and maintaining archives. .....................................................................................................3
5. ci(1) and co(1). ....................................................................................................................................3
6. Revision histories. ...............................................................................................................................4
7. Including RCS data in working files. ..................................................................................................4
8. RCS and emacs(1) Version Control. ...................................................................................................4
i
115287116.001.png
The RCS MINI−HOWTO
Robert Kiesling
v1.4, 14 August 1997
This document covers basic installation and usage of RCS, the GNU Revision Control System, under Linux. It
also covers the installation of the diff(1) and diff3(1) utilities, which are necessary for RCS to
operate. This document may be reproduced freely, in whole or in part, provided that any usage of this
document conforms to the general copyright notice of the HOWTO series of the Linux Documentation
Project. See the file COPYRIGHT for details. Send all complaints, suggestions, errata, and any miscellany to
kiesling@terracom.net , so I can keep this document as complete and up to date as possible.
RCS, the revision control system, is a suite of programs that tracks changes in text files and controls shared
access to files in work group situations. It is generally used to maintain source code modules. It lends itself to
tracking revisions of document files as well.
RCS was written by Walter F. Tichy and Paul Eggert. The latest version which has been ported to Linux is
RCS Version 5.7. There is also a semi−official, threaded version available. Much of the information in this
HOWTO is taken from the RCS man pages.
RCS includes the rcs(1) program, which controls RCS archive file attributes, ci(1) and co(1) , which
check files in and out of RCS archives, ident(1) , which searches RCS archives by keyword identifiers,
The RCS MINI−HOWTO
1
115287116.002.png
The RCS MINI−HOWTO
rcsclean(1) , a program to clean up files that are not being worked on or haven't changed,
rcsdiff(1) , which runs diff(1) to compare the revisions, rcsmerge(1), which merges two RCS
branches into a single working file, and rlog(1), which prints RCS log messages.
Files archived by RCS may be text of any format, or binary if the diff program used to generate change
files handles 8−bit data. Files may optionally include identification strings to aid in tracking by ident(1) .
RCS uses the utilities diff(1) and diff3(3) to generate the change files between revisions. A RCS
archive consists of the initial revision of a file, which is version 1.1, and a series of change files, one for each
revision. Each time a file is checked out of an archive with co(1) , edited, and checked back into the archive
with ci(1) , the version number is increased, for example, to 1.2, 1.3, 1.4, and so on for successive
revisions.
The archives themselves commonly reside in a ./RCS subdirectory, although RCS has other options for
archive storage.
For an overview of RCS, see the rcsintro(1) manual page.
RCS needs diff(1) and diff3(3) to generate the context diff files between revisions. The diff utilities
suite needs to be installed on your system, and when you install RCS, the software will check for its presence.
Precompiled diffutils binaries are available at:
ftp://sunsite.unc.edu/pub/Linux/utils/text/diffutils−2.6.bin.ELF.tar.gz
and its mirror sites. If you need to compile diff(1) , et al., from source, it is located at:
ftp://prep.ai.mit.edu/pub/gnu/diffutils−2.7.tar.gz
and its mirror sites.
You will also need to have the ELF libraries installed on your system if you want to install pre−built binaries.
See the ELF−HOWTO for further details.
Get the source distribution of RCS Version 5.7. It is available at
ftp://sunsite.unc.edu/pub/Linux/devel/vc/rcs−5.7.src.tar.gz
and its mirrors. After you have unpacked the archive into your source tree, you need to configure RCS for
your system. This is done via the configure script in the source directory, which you need to execute first.
This will generate a Makefile and the appropriate conf.sh for your system. You can then type
make install
2. System requirements.
2
115287116.003.png
The RCS MINI−HOWTO
which will build the binaries. At some point you may need to su to root so the binaries can be installed in the
correct directories.
The program rcs(1) does the work or creating archives and modifying their attributes. A summary of
rcs(1) options may be found in the rcs(1) manual page.
The easiest way to create an archive is first to mkdir RCS in the current directory, then initialize the archive
with the
rcs −i name_of_work_file
command. This creates and archive with the name ./RCS/name_of_work_file,v and requests a text
message describing the archive, but it does not deposit any revisions in the archive. You can turn on or off
strict archive locking with the commands
rcs −L name_of_work_file
and
rcs −U name_of_work_file
respectively. There are other options for controlling access to the archive, setting its format, and setting
revision numbers, which are covered in the rcs(1) manual page.
ci(1) and co(1) are the commands used to check files in and out of their RCS archives. The
ci(1) command may also be used to a check a file both in and out of an archive. In their simplest forms,
ci(1) and co(1) take only the name of the working file.
ci name_of_work_file
and
co name_of_work_file
The command form
ci −l name_of_work_file
checks in the file with locking enabled, and
co −l name_of_work_file
is performed automatically. That is, ci −l checks the file out again with locking enabled.
ci −u name_of_work_file
4. Creating and maintaining archives.
3
115287116.004.png

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika:

Zgłoś jeśli naruszono regulamin