Sponsored Content
Top Forums UNIX for Dummies Questions & Answers RCS, what is it? how do i install it... Post 519 by Neo on Thursday 7th of December 2000 09:00:27 PM
Old 12-07-2000
RCS--A System for Version Control

RCS is a standard UNIX utility for version control. RCS comes as a part of most UNIX distibutions 'out-of-the-box'. Snippet from the man page:

Quote:

RCS(1)

NAME
rcs - change RCS file attributes

SYNOPSIS
rcs options file ...

DESCRIPTION
rcs creates new RCS files or changes attributes of existing ones. An RCS file contains multiple revisions ot text, an access list, a change log, descriptive text, and some control attributes.
RCS is available as open source GNU software. Could someone post a link to the MIT GNU archive on the net for the poster?
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

RCS Question

I am a new user. Can anyone tell me where I can get documentation on the RCS feature? Thanks (1 Reply)
Discussion started by: Terry
1 Replies

2. UNIX for Advanced & Expert Users

rcs,sccs

I am not really sure whether i am posting this question in the right forum.....Can someone tell me why I should go for a rational Clearcase version controller when I can use the version controllers 'rcs' or 'sccs' available in UNIX. I want to know the advantage of Rational over these two. Also, I... (2 Replies)
Discussion started by: Abhishek Ghose
2 Replies

3. UNIX for Dummies Questions & Answers

Rcs

does anyone know if RCS is part of UNIX? Does a copy come with all UNIX systesm? Is it a seperate program? Is it purchased? Or is RSC a freeware program downloaded for everyone to use? (3 Replies)
Discussion started by: rtoba
3 Replies

4. Shell Programming and Scripting

creating an RCS archive in /etc

Hi Why is creating an RCS archive in /etc a "good thing"? Hi Why is creating an RCS archive in /etc a "good thing"? (2 Replies)
Discussion started by: scofiled83
2 Replies

5. Shell Programming and Scripting

RCS archive in /etc

Well it is not a bad idea. I have worked for one place that did that. It wasn't my idea but I did not object. The reason it is done is to put critical files like nsswitch.conf, hosts, and so on under RCS control. Previous versions are then available to see how stuff changed over the years. ... (0 Replies)
Discussion started by: Perderabo
0 Replies

6. UNIX for Dummies Questions & Answers

RCS Issue

Hi there, I am trying to utalise RCS on unix. I am including the following tags in my source code for RCS to populate based on rlog. #$Author:$ #$Log:$ Everything i have read on the "co" man page of RCS indicates that the lines from the Log will be populated in the source file using the same... (0 Replies)
Discussion started by: cdoyle
0 Replies

7. Linux

Migrating RCS from HP-UX to Linux

Hello all, We would be migrating from HP-UX 11 to Red Hat Linux 5 shortly. On HP-UX we've been using RCS (Revision Control system). On RHEL I think there is an equivilant utility called Subversion..Is there a way to export the current contents from RCS in HP-UX and import it into Linux's... (2 Replies)
Discussion started by: luft
2 Replies

8. UNIX for Dummies Questions & Answers

suppress RCS messages

ci filename This command displays a message. I don't want it to. How can I keep RCS from doing so? (5 Replies)
Discussion started by: robin_simple
5 Replies
RCSCLEAN(1)						      General Commands Manual						       RCSCLEAN(1)

NAME
rcsclean - clean up working files SYNOPSIS
rcsclean [options] [ file ... ] DESCRIPTION
rcsclean removes files that are not being worked on. rcsclean -u also unlocks and removes files that are being worked on but have not changed. For each file given, rcsclean compares the working file and a revision in the corresponding RCS file. If it finds a difference, it does nothing. Otherwise, it first unlocks the revision if the -u option is given, and then removes the working file unless the working file is writable and the revision is locked. It logs its actions by outputting the corresponding rcs -u and rm -f commands on the standard output. Files are paired as explained in ci(1). If no file is given, all working files in the current directory are cleaned. Filenames matching an RCS suffix denote RCS files; all others denote working files. The number of the revision to which the working file is compared may be attached to any of the options -n, -q, -r, or -u. If no revision number is specified, then if the -u option is given and the caller has one revision locked, rcsclean uses that revision; otherwise rcsclean uses the latest revision on the default branch, normally the root. rcsclean is useful for clean targets in makefiles. See also rcsdiff(1), which prints out the differences, and ci(1), which normally reverts to the previous revision if a file was not changed. OPTIONS
-ksubst Use subst style keyword substitution when retrieving the revision for comparison. See co(1) for details. -n[rev] Do not actually remove any files or unlock any revisions. Using this option will tell you what rcsclean would do without actually doing it. -q[rev] Do not log the actions taken on standard output. -r[rev] This option has no effect other than specifying the revision for comparison. -T Preserve the modification time on the RCS file even if the RCS file changes because a lock is removed. This option can suppress extensive recompilation caused by a make(1) dependency of some other copy of the working file on the RCS file. Use this option with care; it can suppress recompilation even when it is needed, i.e. when the lock removal would mean a change to keyword strings in the other working file. -u[rev] Unlock the revision if it is locked and no difference is found. -V Print RCS's version number. -Vn Emulate RCS version n. See co(1) for details. -xsuffixes Use suffixes to characterize RCS files. See ci(1) for details. -zzone Use zone as the time zone for keyword substitution; see co(1) for details. EXAMPLES
rcsclean *.c *.h removes all working files ending in .c or .h that were not changed since their checkout. rcsclean removes all working files in the current directory that were not changed since their checkout. FILES
rcsclean accesses files much as ci(1) does. ENVIRONMENT
RCSINIT Options prepended to the argument list, separated by spaces. A backslash escapes spaces within an option. The RCSINIT options are prepended to the argument lists of most RCS commands. Useful RCSINIT options include -q, -V, -x, and -z. RCS_MEM_LIMIT An integer lim, measured in kilobytes, specifying the threshold under which commands will try to use memory-based operations for processing the RCS file. (For RCS files of size lim kilobytes or greater, RCS will use the slower standard input/output routines.) Default value is 256. TMPDIR Name of the temporary directory. If not set, the environment variables TMP and TEMP are inspected instead and the first value found is taken; if none of them are set, a host-dependent default is used, typically /tmp. DIAGNOSTICS
The exit status is zero if and only if all operations were successful. Missing working files and RCS files are silently ignored. IDENTIFICATION
Author: Walter F. Tichy. Manual Page Revision: 5.9.0; Release Date: 2014-06-10. Copyright (C) 2010-2013 Thien-Thi Nguyen. Copyright (C) 1990, 1991, 1992, 1993 Paul Eggert. Copyright (C) 1982, 1988, 1989 Walter F. Tichy. SEE ALSO
ci(1), co(1), ident(1), rcs(1), rcsdiff(1), rcsmerge(1), rlog(1), rcsfile(5). Walter F. Tichy, RCS--A System for Version Control, Software--Practice & Experience 15, 7 (July 1985), 637-654. The full documentation for RCS is maintained as a Texinfo manual. If the info(1) and RCS programs are properly installed at your site, the command info rcs should give you access to the complete manual. Additionally, the RCS homepage: http://www.gnu.org/software/rcs/ has news and links to the latest release, development site, etc. BUGS
At least one file must be given in older Unix versions that do not provide the needed directory scanning operations. GNU RCS 5.9.0 2014-06-10 RCSCLEAN(1)
All times are GMT -4. The time now is 05:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy