Marc G. Fournier has a great idea:
> I don't know if anyone has tried this yet, and I've only just
> barely tried it here...
>
> If you take the README.cvsup file that is found at
> ftp.postgresql.org:/pub/CVSup and comment out the line that states
> '*default tag=.', it will pull down the actual RCS files.
>
> So, for instance, if you were to setup a CVS repository on your
> machine and, using the above, pull the RCS files into $CVSROOT (and
> created an appropriate $CVSROOT/CVSROOT directory), you could grab the
> current source tree easily, and then checkout (and update) a local source
> tree)...
>
> Then you'd just have to send in patches periodically, while
> keeping your local source tree in sync with the master...
This sounds like exactly what I was looking for. So I am still a little hazy
on the interaction between CVS and cvsup so perhaps you could spell this
out a bit:
Suppose I want to work in ~/pgsql and refer to the module as pgsql. And I want
to store all my CVS trees under /local1/cvsroot. If I have understood you
I need to do
export CVSROOT=/local0/cvsroot
cvs init $CVSROOT
mkdir $CVSROOT/CVSROOT # is this right? why?
cat >$CVSROOT/modules
pgsql ??? what goes here ???
^D
And then how do I keep in sync with the master?
I am embarrassed to keep asking about this, I really do know about databases,
but I have never used CVS and cvsup so all help is appreciated.
Thanks
-dg
David Gould dg@illustra.com 510.628.3783 or 510.305.9468
Informix Software (No, really) 300 Lakeside Drive Oakland, CA 94612
"I was pleased to be able to answer right away, and I did.
I said I didn't know." -- Mark Twain, Life on the Mississippi
