Arthur Barrett escribió:
Michael,
I'm a CVS newbie and having problems working with
two different repositories on the same working copy.
This is extremely complex to set up - your local repository needs to be
a write through cache.
I'm not sure how you'd do this with CVS, but these posts explain how to
do it with CVSNT:
http://www.cvsnt.org/pipermail/cvsnt/2008-May/030637.html
And
http://www.cvsnt.org/pipermail/cvsnt/2008-May/030642.html
And
http://www.cvsnt.org/pipermail/cvsnt/2008-May/030653.html
And
http://www.cvsnt.org/pipermail/cvsnt/2008-May/030655.html
And
http://www.cvsnt.org/pipermail/cvsnt/2008-May/030659.html
Repository replication is almost never needed - CVS is designed to work
without it even over very slow networks or while a developer is offline
for long periods of time.
After having read the docs and the archives to this list,
I still don't understand how I could update my working
copy from the main repository (REP1). Whenever I try this,
I get a "cannot open directory" error.
You need to send the newsgroup the actual commands you are using and the
actual (compelte) error message including the 'connection string' (also
called the CVSROOT) that looks like:
* :pserver:a...@host:/repo
* :local:host:/var/opt/blah
* etc
Regards,
Arthur Barrett
Hello Arthur,
thanks so much for your hints.
I've checked out my project from the local repository like this (CVSROOT
environment variable is set to /cvsroot):
/var/parent/#> cvs checkout packages
No I would like to update one subdirectory ("package") of the project
from the remote server like this:
/var/parent/#> cvs -z3 -d
:pserver:[email protected]:/home/cvsroot update package_name
Then I get the following error message:
cvs update: cannot open directory /home/cvsroot/packages/package_name:
No such file or directory
Thanks,
Michael