>--- Forwarded mail from [EMAIL PROTECTED] >Lynch, Harold <[EMAIL PROTECTED]> writes:
>> This may be a wierd one.=20 >>=20 >> If there are two different repositories on one machine, would it be a >> "bad" thing to link part of one repository to the other. >>=20 >> I.E. >>=20 >> if there is a module in repository A call whatever, and the dir is >> linked to repository B will the cvs server (we are using pserver >> method), handle it correctly? >I will assume that by 'linked' you mean that one of the repositories has >a symbolic link to the directory in the other repository... >You will NOT be able to use LockDir with either of the repositories >involved. You will also need to take care that the commit criteria of >your CVSROOT *info scripts are consistent across both repositories... >You will also want to have a consistent understanding of how your users >map across both repositories. In fact, you will probably end up with >a great deal of CVSROOT being duplicated between the two to get this >to work. So, you need to ask yourself why you even bother to have two >separate repositories on the machine... >That said, I have not tried the setup you suggest. It might work, but it >is probably not the best idea I have seen mentioned. I have used such a method successfully in the past, but I would not recommend it. It's much better to write the overlap into your modules definitions, though that method also has its limitations. >--- End of forwarded message from [EMAIL PROTECTED] _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs