[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RES: Repository hierarchy
From: |
Marcelo Carvalho Fernandes |
Subject: |
RES: Repository hierarchy |
Date: |
Tue, 4 May 2004 17:46:37 -0300 |
Mohit,
I think you are trying to do the same thing as xyzzy. Take a look at "Module
aliases" thread.
Let me know if it works because I´ve tested Jim.Hyslop's solution but it
doesn't work.
--------------------------
Marcelo Carvalho Fernandes
Smart Tech Consulting
www.smartech.com.br
Tel:(55)21-2532-6335
-----Mensagem original-----
De: address@hidden
[mailto:address@hidden nome de
address@hidden
Enviada em: terça-feira, 4 de maio de 2004 03:14
Para: CVS list
Assunto: Repository hierarchy
Hi
I have a CVSROOT tree structure like this:
/cvsroot
|
---business1_module1
|
---business1_module2
|
---business1_module3
.
.
|
---business2_module1
|
---business2_module2
|
---business2_module3
Certain new modules have come up for development which are logically a part
of the existing ones, but would be developed independently.
My first question: Should I create a separate module altogether? (like
business1_module1_1 .... )
If I plan to create it *inside* business1_module1(so that I don't clutter
up /cvsroot with 100's of projects) , I would have to make changes to the
'modules' file. I did this:
business1_module1_1 -d business1_module1/business1_module1_1
business1_module1 -d !business1_module1/business1_module1_1
business1_module1
However, when I do a checkout of business1_module1_1, the sandbox first has
the subdirectory business1_module1.
Question: How do I have business1_module1_1 as the 'root' module directory
on my sandbox?
Finally, is there any set of guidelines that a CVS administrator should
follow on the repository hierarchy when a large number of
projects/sub-projects exist?
TIA !
---
Mohit
- Repository hierarchy, mohit . suley, 2004/05/04
- RES: Repository hierarchy,
Marcelo Carvalho Fernandes <=