Re: [ jEdit-devel ] cvs

[mike d. <md...@st...>]

On Thu, 23 Mar 2000, D. David Pirzadeh wrote:
> cvs -z3 -d:pserver:ano...@cv...:/cvsroot/jedit co 
> modulename
>      ^^^^^^ THIS IS THE KEY - "plugins" works for me but I don't get
>             the rest of the files. and it exports into my current
>             directory. (I use NT)

aha! i figured out what the problem is. for cvs commands, there are two
sets of options, the spec is like so:

cvs [ cvs_options ] cvs_command [ command_options ] [ command_args ]

there is a '-d' option for both cvs_options and the command_options for
'checkout'. in the cvs_options (as you are using it above), '-d' means
"Use the following value as the CVSROOT, instead of the value of the
CVSROOT env. variable or the current directory." as a command option for
'checkout' (as well as 'export'), '-d' means "Use the following directory
for the check out instead of the module name."

so, your command should be:

cvs -z3 -d:pserver:ano...@cv...:/cvsroot/jedit co \
	-d "C:\Program Files\jEdit-2.4cvs\jars" plugins


> Updates from within the module's directory do not need the -d parameter.
>            !! I have no clue what this means

this means that if you do a checkout (not an export), and later want to
update your files, you don't have to use the cvs_option -d. instead, you
can go to the directory where you did the check-out (i.e. the lowest
directory with a CVS sub-directory), and simply do:

cvs -z3 login
cvs -z3 update

this is because the CVSROOT for a working directory created by a check out
is stored in the file CVS/Root.

> -Basically I would love to know what module name or names I can
> use to get the source code to come through

????

-md