RE: Importing then checking out?

[Jim.Hyslop]

Galen Boyer wrote:
> Okay,
> 
[...]
> So, I'm trying to import sources for ecb-1.93.  I do the
> following:
> 
>   $ cd ecb-1.93
>   $ cvs import -m "Import of FSF ECB v. 1.93" 
> grersrepository/ecb FSF_DIST ECB_1_93
> 
> I get the following:
> 
>    No conflicts created by this import
> 
> Okay, now I try to commit this (I assume I need to commit?)
Nope - import is one of the few commands that do not require a commit.

[...]
> Okay, so I try to check this out:
> 
>    $ cd ../ecb
>    $ cvs checkout ecb
> 
> And I get:
> 
>    cvs server: cannot find module `ecb' - ignored cvs1 
> [checkout aborted]:
>    cannot expand modules
> 
> QUESTIONS:
> 
> Our repository name is grersrepository.  What is the "/" for?
Same as any other path specifier ;-)

The "repository" argument to import specifies the subdirectory within the
repository, where you want to place the files. So, the command that you
issued above imported the source into the directory
$CVSROOT/grersrepository/ecb, where $CVSROOT is the root of your repository
(in your case, /grersrepository).

> Is
> ecb a module, or do I consider it a new repository?
Any command that takes an argument "modules" looks up the specified modules
in the CVSROOT/modules file. If you want 'ecb' to be a CVS module, then you
need to check out CVSROOT, modify the 'modules' file then check it back in
(see https://www.cvshome.org/docs/manual/cvs-1.11.18/cvs_18.html#SEC159 for
details on the modules file). 

Actually, there is one argument for "modules" that is not looked up in the
modules file: the period. The command "cvs checkout ." will check out the
entire repository. So, if you don't want to create a module, you can issue
the command:

cvs checkout ./grersrepository/ecb

-- 
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. ( http://www.leitch.com )
Columnist, C/C++ Users Journal ( http://www.cuj.com/experts )