Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Mon, 24 Jan 2005 22:58:30 +0000 (UTC), "Oliver Giesen" <ogware at gmx.net> wrote: >> Also if you do this, you will have trouble tagging project1 because >> you would also tag Project2 at the same time. > >Huh? There can only ever be one entry in each ./CVS/Repository file. In >the above (horror) scenario the last module specified wins (if you even >get that far that is - I never tried it - it might well fail on >checkout already). It is technically impossible to tag two repository >modules by tagging a single sandbox folder. What I meant was this: 1) Assuming all binaries are in a single module folder on the server 2) Assuming multiple "projects" are checked out to individual source directories in parallel 3) Also assume that the binary of each all go to the same sandbox folder in the same way as they are on the server. Then the sandbox binaries folder will have a varying number of binaries inside depending on how many "proojects" have been checked out. If there are more than one then more than one projects are also out. When tagging projects one would select the source dir of that project and tag it. But then one also needs to tag the binary and this has to be done by individual selection of that binary file in the binaries folder, because selecting the binaries folder will tag also the binaries of the other projects with the same tag... In any case it is not good to do this at all so enough is enough, don't mix projects in a parallel structure like this! Better to use a separate sandbox for each project where the Include files and binaries are checked out with the sources. Another project will have the same includes again so there is a duplication, but that is no real problem. And it helps to keep the interaction between projects at a minimum, cvs-wise. /Bo (Bo Berglund, developer in Sweden)