On 12/3/06, T. Nguyen <ptn_y2k1@yahoo.com> wrote:
> Hi,
>
> I am setting up a Subversion server. As I read several books and searched on
> the internet, I have not seen any complicated repository structure as my
> workplace requested. Please see the following structure:
>
> svn_root
> dev
> project1_root
> project1_web
> project1_web_v1
> trunk
> tags
> branches
> project1_web_v2
> (trunk,
> tags, branches)
> project1_jobs
> project1_jobs_v1
> (trunk,
> tags, branches)
> project1_jobs_v2
> (trunk,
> tags, branches)
> project2_root
> .....
> .......
> .......
> ........
> project3_root
> qa
> ................(same structure as dev)
>
> Here are my questions that I need your helps.
>
> 1. Is it possible to have that kind of structure in Subversion? If yes, is
> it a good or bad structure? And is it easy to maintain later? If no, please
> give me your advise what I should do?
Yes, it's possible. Is it good or bad, easy or hard to maintain?
That's up to you - how much time you have to devote to it, what (if
any) tools/scripts you can put together to help, your comfort level
with Subversion, etc.
My big question is why version 1 and version 2 aren't branches of the
same project, but instead kept so separate.
> 2. If it's possible, which level should I use 'svnadmin create' and which
> level should I use 'svn mkdir'?
How many repositories do you want? You use svnadmin create once per
repository, and svn mkdir any number of times per repository. I think
you're looking at a single repository here, so you would use svnadmin
create to create the repository "root" itself.
If you haven't read it yet, the book is very helpful. http://svnbook.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 4 16:11:21 2006