Installing suberversion to allow versioning on multiple projects

[Matthew Kidd <Ma...@cappsdigital.com>]

Hi,

I was tasked with the conversion of our versioning system from CVS to subversion. So far things are going smoothly but I am getting confused with the aspect of keeping the versioning separate amongst our several projects and avoid the "synchronous" versioning that would occur if all the projects were in one repository.

The place I am getting confused is right after the "svnadmin create /path/to/repos" that creates the central repository. I don't want that. I want separate repositories for each project that we have resulting in a directory structure like below:

projectA
     /trunk
     /branches
     /tags
projectB
     /trunk
     /branches
     /tags
projectC
     /trunk
     /branches
     /tags
.....etc

Do I need to create central repositories for each project? If so how do the directories created via the "svnadmin create" factor in to the directory structure I want above?

As far as importing the the actual files I have a decent grasp of that as well but that seems to be contingent on the answer to the former question in that I know that I want the files exported from CVS (top skim, no history) placed in the trunk directory but the explanation provided in the Quick Start is a little confusing so I'm unsure of the actual result of performing the import command.

Thanks for any help you can provide. 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Installing suberversion to allow versioning on multiple projects

[Ryan Schmidt <su...@ryandesign.com>]

On Jun 12, 2006, at 23:33, Matthew Kidd wrote:

> The place I am getting confused is right after the "svnadmin  
> create /path/to/repos" that creates the central repository. I don't  
> want that. I want separate repositories for each project that we  
> have resulting in a directory structure like below:
>
> projectA
>      /trunk
>      /branches
>      /tags
> projectB
>      /trunk
>      /branches
>      /tags
> projectC
>      /trunk
>      /branches
>      /tags
> .....etc
>
> Do I need to create central repositories for each project? If so  
> how do the directories created via the "svnadmin create" factor in  
> to the directory structure I want above?

Yes, if you want separate repositories (and separate repository  
revision numbers) for each project, you would "svnadmin create" a  
repository for each project:

svnadmin create /path/to/projectA
svnadmin create /path/to/projectB
svnadmin create /path/to/projectC

And you could then create the empty directory structure in each:

svn mkdir \
file:///path/to/projectA/trunk \
file:///path/to/projectA/branches \
file:///path/to/projectA/tags \
-m "Creating empty trunk / branches / tags directories in projectA"

And so on for the other projects.

If you're serving these repositories with Apache 2, then the easiest  
would be to point to the directory all the repositories are in ("/ 
path/to" in my examples above) using the SVNParentPath directive.


> As far as importing the the actual files I have a decent grasp of  
> that as well but that seems to be contingent on the answer to the  
> former question in that I know that I want the files exported from  
> CVS (top skim, no history) placed in the trunk directory but the  
> explanation provided in the Quick Start is a little confusing so  
> I'm unsure of the actual result of performing the import command.

The "svn import" syntax gets me too if I'm not really concentrating.  
I recommend trying a few imports with different scenarios in a test  
repository to assure yourself you've got the syntax right before  
proceeding to the real import.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Installing suberversion to allow versioning on multiple projects

[Andreas Pakulat <ap...@gmx.de>]

On 12.06.06 16:33:17, Matthew Kidd wrote:
> I was tasked with the conversion of our versioning system from CVS to subversion. So far things are going smoothly but I am getting confused with the aspect of keeping the versioning separate amongst our several projects and avoid the "synchronous" versioning that would occur if all the projects were in one repository.

Among subversion users it's common sense (AFAIK) that you shouldn't care
wether your projects "share" revision numbers or not. Anyway,...

> The place I am getting confused is right after the "svnadmin create /path/to/repos" that creates the central repository. I don't want that. I want separate repositories for each project that we have resulting in a directory structure like below:
> 
> projectA
>      /trunk
>      /branches
>      /tags
> projectB
>      /trunk
>      /branches
>      /tags
> projectC
>      /trunk
>      /branches
>      /tags
> .....etc
> 
> Do I need to create central repositories for each project?

Yes, you need to do exactly that.

> If so how do the directories created via the "svnadmin create" factor in to the directory structure I want above?

Not sure if this is what you mean, but you would to something like

svnadmin create /path/to/where/repos/are/projectA
svnadmin create /path/to/where/repos/are/projectB
svnadmin create /path/to/where/repos/are/projectC

Andreas

-- 
You get along very well with everyone except animals and people.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org