> Yeah. That'd be a cool feature. But then, CVS will no longer be a > standalone program. If you move the repository to another server > where the modules are missing, how would you expect CVS to behave?
The plugins would be part of the module, so if you moved the module to another CVS repository running the same versions of CVS everything would still work perfectly. (or if you moved the entire repository) > Consider the case where programmers are working on UNIX workstations > with an NFS mounted CVS repository. The "cvs" command just runs > locally, without using the CVS client-server operations. In this > case, it is possible that those pluggable modules are present on some > workstations but not the others. So, files commited from one machine > may fail to check out in another. And how can we now make sure the > snapshots (tags) is really reproducible, when CVS now depends on > extension modules? CVS would have to use a thin client, and the diff/merge program would have to be on executed on the server side. This would ensure that rules are enforced correctly. Sean. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
