ADC Home > Reference Library > Reference > Mac OS X > Mac OS X Man Pages

 

This document is a Mac OS X manual page. Manual pages are a command-line technology for providing documentation. You can view these manual pages locally using the man(1) command. These manual pages come from many different sources, and thus, have a variety of writing styles.

This manual page is associated with the Mac OS X developer tools. The software or headers described may not be present on your Mac OS X installation until you install the developer tools package. This package is available on your Mac OS X installation DVD, and the latest versions can be downloaded from developer.apple.com.

For more information about the manual page format, see the manual page for manpages(5).



RCSCLEAN(1)                                                                                      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 stan-dard standard
       dard output.

       Files are paired as explained in ci(1).  If no file is given, all working files in the current direc-tory directory
       tory  are  cleaned.   Pathnames  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 differ-ences, differences,
       ences, 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  sup-press suppress
              press  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 com-mands. commands.
              mands.  Useful RCSINIT options include -q, -V, -x, and -z.

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: 1.1; Release Date: 1999/04/23.
       Copyright (C) 1982, 1988, 1989 Walter F. Tichy.
       Copyright (C) 1990, 1991, 1992, 1993 Paul Eggert.

SEE ALSO
       ci(1), co(1), ident(1), rcs(1), rcsdiff(1), rcsintro(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.

BUGS
       At least one file must be given in older Unix versions that do not provide the needed directory scan-ning scanning
       ning operations.



GNU                                              1999/04/23                                      RCSCLEAN(1)

Did this document help you?
Yes: Tell us what works for you.
It’s good, but: Report typos, inaccuracies, and so forth.
It wasn’t helpful: Tell us what would have helped.