New to CVS Need help setting up repo

[stacy . j . lyons]

I have set up a test area and have been playing around with creating
repositories.  I successfully set up a single subdir containing source code
but I am
trying to set up a repository containing multiple subdirectories with
source code in them.  My dir structure is as follows and I initiated the
following commands.

/cpas/stacy/cvs/incmar01/pub   (Both pub and src contain source code)
src

$pwd
/cpas/stacy/cvs/incmar01

$cvs -d /cpas/stacy/cvs/incmar01/ init
(This gives me CVSROOT)
$cvs import -m init inc stacy start
(Here is where I get problems.  The following scrolls on the screen until I
stop it)

N inc/inc/inc/inc/inc/inc/src/inctabu1.sas,v,v,v,v,v


When I successfully did this before I cd'ed to the pub dir and did the
import.  This worked but I don't want to have multiple repositories for
each individual subdir.  How do I place multiple subdirs with source code
into the repository???


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: New to CVS Need help setting up repo

[Larry Jones]

[EMAIL PROTECTED] writes:
 
 $pwd
 /cpas/stacy/cvs/incmar01
 
 $cvs -d /cpas/stacy/cvs/incmar01/ init
 (This gives me CVSROOT)
 $cvs import -m init inc stacy start
 (Here is where I get problems.  The following scrolls on the screen until I
 stop it)
 
 N inc/inc/inc/inc/inc/inc/src/inctabu1.sas,v,v,v,v,v

Your CVSROOT should be a *brand new* directory, not an existing
directory that contains source code you want to put under CVS control. 
Think of the repository as a library.  If you have books that you want
to put in a library, you don't build a library around where the books
already are, you build it somewhere else and then take the books to it. 
CVS works the same way: init builds the library and import takes
(copies) your files into it.

Reasonably recent versions of CVS won't let you import inside the
library and get the infinite recursion you reported.  You really should
upgrade.

-Larry Jones

Is it too much to ask for an occasional token gesture of appreciation?!
-- Calvin

___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs