Hi, Andy, Johnathan and Matt:
First of all, I would like to say thank you to three of you for helping me. Second thing is I would like to clear up my repository structure. I knew I confused all of you, sorry about that.
1. project1_web_v1 should be the current project (go live already). For each release such as v1.1.10 or v1.1.11 is under this project. We did branch it out and merge it back in CVS. We are going to do the same thing when we convert to SVN.
2. project1_web_v2 is a future project of project1_web_v1. We're planning to redesign it with new technology.
3. project1_web and project1_jobs are related, therefore I put these two projects under the same root.
4. project1_root, project2_root and project3_root are not related.
5. qa doesn't have the same projects as dev... (I used wrong words, then make all of you confused, sorry about that). It means that qa has the same many subfolders as dev. I listed it out because I would like to let you know that I have several folders (dev, qa, and etc.) under svnroot.
I hope that my above explanations help all of you understand what I meant.
By the way, when I run "svn mkdir newdir", I got the following error:
$ svn mkdir testing
subversion/libsvn_wc/lock.c:591: (apr_err=155007)
svn: '.' is not a working copy
subversion/libsvn_subr/io.c:2473: (apr_err=2)
svn: Can't open file '.svn/entries': No such file or directory
$
Do you know why I got this error? Please note that I am currently using subversion-1.4.2. I got the same error in v1.4.0 and 1.3.x.
Thank you all of you very much. Your answers are really helpful to me. I am looking forward to hear from you again.
Best Regards,
T.
Matt Sickler <crazyfordynamite@gmail.com> wrote:
why are v1 and v2 so separate?
why are there different sections for QA and dev?
On 12/2/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?
2. If it's possible, which level should I use 'svnadmin create' and which level should I use 'svn mkdir'?
I am looking forward to receiving your response. Thank you very much.
Regards,
Tracy
---------------------------------
Have a burning question? Go to Yahoo! Answers and get answers from real people who know.
---------------------------------
Check out the all-new Yahoo! Mail beta - Fire up a more powerful email and get things done faster.
Received on Wed Dec 6 03:12:33 2006