The only way your idea works is if the CVS server is carefully
architected to separate the storage mechanism from the rest of the code.
I don't know if it is, and apparently no one answering on this list does
either, which is itself a bad sign. 

Are you looking for dual interface capabilities, i.e. People can
checkout/in, label, branch, etc. using ClearCase and CVS concurrently? 
The closest thing to a reasonable sounding approach to doing this came
from Noel L Yap:
> It might be easier instead to create scripts that look like CVS, 
> but calls CC underneath.
However, if you are also hoping to set up a remote CVS server this won't
work - you need all the network code from CVS. 

If you don't need update access from both CVS and CC, I would create two
repositories where one is a read-only replica of the other. Automating
replication in one direction sounds much easier than what you describe. 

Good Luck and keep us posted,
Jim Melton.

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

Reply via email to