|Subject:||Info about project structuring|
|Date:||Thu, 12 Sep 2002 16:24:45 +0900|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827|
Hello,I have been surfing a quite bit to find information about what is important when structuring a project managed in CVS. The project has a pretty clear structure, but I still do not know what these project modules/sub-projects etc. should map to in the CVS world.
Example:We can make a project module map to a CVS module. So that we can checkout only that portion of the project, and not bother about the other parts. Also, with the CVSROOT/modules file, we can define entire projects, which checkout all the necessary thigs, enable some level of module bundling. However, the same could be achieved in making it a single CVS module and playing with Makefile/build.xml files to compile/bundle/run only a portion of the whole.
Where can I find information about the impact of such decision have on the life of a project ? Pros&cons, good and bad experiences welcome :-)
|[Prev in Thread]||Current Thread||[Next in Thread]|