From: Vincent Fourmond Date: 2007-01-19T21:05:59+09:00 Subject: Re: rubyforge.org questions Tom Copeland wrote: > On Fri, 2007-01-19 at 20:42 +0900, Peter Szinek wrote: > >> However, there is a small (not unsolvable, but ATM existing) problem >> here: you everywhere have instructions for anonymous checkout like this: >> >> svn checkout svn://rubyforge.org/var/svn/some_project >> >> Now, if you leave it like this, and some people will begin to use the >> trunk-tags-branches or whatever model, there could be some confusion - >> (i.e. there will be no some_project directory, but trunk and branches >> instead). However, this could be resolved by automatically adding a >> symlink to trunk/some_project. Just a suggestion... symlink is not possible (at least from what I know) in subversion. /var/svn/some_project is a *real* directory, and everything under it is a 'virtual' directory which doesn't appear on the filesystem, but rather in the subversion databases. > Hm... yup... any svn experts want to weigh in here? I mean, is it > standard svn practice to do the trunk/branches/tags directory structure? I'm not an expert, but so far, I've seen only this. But it is not a good idea to set it up by default. Some projects want to have only one 'main directory' in their repository, so that it would look like svn://rubyforge.org/var/svn/some_project/trunk svn://rubyforge.org/var/svn/some_project/branches svn://rubyforge.org/var/svn/some_project/tags But some other want subprojects, and will use the following: svn://rubyforge.org/var/svn/some_project/subproject_1/trunk svn://rubyforge.org/var/svn/some_project/subproject_1/branches svn://rubyforge.org/var/svn/some_project/subproject_1/tags and so on for other subprojects. My opinion is to add a FAQ element with the instructions on how to create a standard some_project/(trunk|tags|branches) structure (with mkdir, pretty fast), and leave those who prefer another structure to do it themselves (they should know ;-)...) Finally, I would say that usually, you check out a svn repository with the following command: svn co svn+ssh://deve@rubyforge.org/var/svn/some_project/trunk some_project This way, the trunk directory is mapped as a some_project directory on your local copy: it is much easier to work on. Cheers ! Vince -- Vincent Fourmond, PhD student http://vincent.fourmond.neuf.fr/