Peter Sotos wrote: > I have a lot of corporate data which I want to store in CVS. > This ranges > from RTF Office Policy Documents to Source Code. I don't want > to have 100's > of modules in a single repository because it would become > difficult to find > which module you wanted. On the contrary, a well-organized CVSROOT/modules file will make it *easier* to find the module you want. Instead of checking out this/that/other/blah/mymodule you just check out mymodule. Done.
> I thought about having 3 modules (src, docs, websites), but > then the module > listing command in wincvs would never give you a good listing of the > repositories in cvs. It seems to me splitting your data across different repositories will actually make this worse - instead of connecting to one repository and browsing a single set of modules, now you have to connect to three different repositories to find what you want. > Also, I am unfamiliar with how > sub-modules work. I have > heard that you can have them but not sure of the > implementation details > (imports/checkouts/etc with sub modules). Also, how can I get > a list of all > of the sub modules for a particular module? I don't use WinCVS, but from the command line you can just type cvs co -c and it will list the contents of the modules file. > In any case, has any had to deal with a problem like I am > having? If so, > what were your approaches to it? Single repository, well-organized modules file. We have 193 modules listed in the file (including modules used just to experiment with CVS). -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
