CVS real-life examples Post: 30237

Sponsored Content

Top Forums UNIX for Advanced & Expert Users CVS real-life examples Post 30237 by RTM on Friday 18th of October 2002 09:48:07 AM

10-18-2002

Registered User

CVS and Solaris are good enough friends. We use it to keep our NIS files from being screwed up by more than one admin (of course, that was when we had 14 admins versus the 3 still here - now it's not as big a deal).

From the man page:

CVS is a version control system, which allows you to keep
old versions of files (usually source code), keep a log of
who, when, and why changes occurred, etc., like RCS or SCCS.
Unlike the simpler systems, CVS does not just operate on one
file at a time or one directory at a time, but operates on
hierarchical collections of directories consisting of ver-
sion controlled files. CVS helps to manage releases and to
control the concurrent editing of source files among multi-
ple authors. CVS allows triggers to enable/log/control
various operations and works well over a wide area network.

cvs keeps a single copy of the master sources. This copy is
called the source ``repository''; it contains all the infor-
mation to permit extracting previous software releases at
any time based on either a symbolic revision tag, or a date
in the past.
Home of CVS
CVS Docs has information on why,what, how.

SCCS which comes with Solaris is lousy for SAs since it sets file permissions to read-only instead of leaving the permissions the way they were.

RCS is just as good as CVS except you have to remember to check the file out first (RCS is being used for DNS zone files but CVS would work too).

RTM

View Public Profile for RTM

Find all posts by RTM

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

looking for .profile examples

I'm looking for some 'well documented' .profile examples

2. Shell Programming and Scripting

need examples?

Can someone give me an example of two shells?

3. UNIX for Advanced & Expert Users

Most useful Unix commands and Examples

These commands are placed in the MS Word Doc. with command options and the their respective examples. hope this will help for the beginners. Thanks. Varun Gupta:D

4. UNIX for Advanced & Expert Users

End of Life / Life Cycle Information

Hello everyone, I was searching for locations where I can get End of Life information on multiple versions of Unix. I have found some information which I list below, what I have not found or confirmed is where I can get the information for: DEC Unix/OSF1 V4.0D NCR Unix SVR4 MP-RAS Rel 3.02....

5. UNIX for Dummies Questions & Answers

SimpleAWK Examples

Can Anyone please give me some simple AWK Examples to clearly understand the usage and syntax of the command. Thanks

6. Shell Programming and Scripting

Need lot of examples

Hi, I need a word doc or pdf which contains lots of Shell Programming samples... This is for my open book examination, thanks in advance..

LEARN ABOUT XFREE86

cvs-debc

CVS-DEBC(1)						      General Commands Manual						       CVS-DEBC(1)

NAME

       cvs-debc - view contents of a cvs-buildpackage/cvs-debuild generated package

SYNOPSIS

       cvs-debc [options] [package ...]

DESCRIPTION

       cvs-debc  is  run  from the CVS working directory after cvs-buildpackage or cvs-debuild.  It uses the cvs-buildpackage system to locate the
       .changes file generated in that run.  It then displays information about the .deb files which were generated in that run, by running  dpkg-
       deb -I and dpkg-deb -c on every .deb archive listed in the .changes file, assuming that all of the .deb archives live in the same directory
       as the .changes file.  It is useful for ensuring that the expected files have ended up in the Debian package.

       If a list of packages is given on the command line, then only those debs with names in this list of packages will be processed.

       Note that unlike cvs-buildpackage, the only way to specify the source package name is with the -P option; you cannot simply have it as  the
       last command-line parameter.

OPTIONS

       All  current  cvs-buildpackage options are silently accepted; however, only the ones listed below have any effect.  For more details on all
       of them, see the cvs-buildpackage(1) manpage.

       -adebian-architecture, -tGNU-system-type
	      See dpkg-architecture(1) for a description of these options.  They affect the search for the .changes file.  They  are  provided	to
	      mimic the behaviour of dpkg-buildpackage when determining the name of the .changes file.

       -Mmodule
	      The name of the CVS module.

       -Ppackage
	      The name of the package.

       -Vversion
	      The version number of the package.

       -Ttag  The CVS tag to use for exporting sources.

       -Rroot directory
	      Root of the original sources archive.

       -Wwork directory
	      The full path name for the cvs-buildpackage working directory.

       -xprefix
	      This option provides the CVS default module prefix.

       --help, --version
	      Show help message and version information respectively.

SEE ALSO

       cvs-buildpackage(1), cvs-debi(1), cvs-debuild(1) and debc(1).

AUTHOR

       cvs-buildpackage was written by Manoj Srivastava, and the current version of debi was written by Julian Gilbey <jdg@debian.org>.  They have
       been combined into this program by Julian Gilbey.

DEBIAN
								 Debian Utilities						       CVS-DEBC(1)