[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Repository layout

From: Nicklas Norling <nicklas.norling_at_ifsab.se>
Date: 2004-03-23 13:55:05 CET

> -----Original Message-----
> From: Tom Vergote [mailto:tom@tomvergote.be]

> 1. Create a repository under the reporoot and import
> directory's for the projects? Where would trunks and branches
> be layed out? If I understand correctly with this setup a
> commit in proj1 for custA would updatethe revision for all
> projects in all customers.

A commit is global to the repo, so yes, the revision will be increased
for all customers and projects for each change.
Having global revisions ticking away when there is no change feels strange
to begin with, but one get's used to it, and it becomes very handy
to have each change "tagged" with a revision.

> 2. follow along the directory structure but create
> repositorys in each project, and then import
> trunk/tags/branches dir's in each projects repository.

I'd stick with one repo. Projects and even customers may have
stuff in common, and having them in one repo makes it easier
to make code changes to many in one revision.

Also proj1/trunk or trunk/proj1 that's difficult, maybe a
matter of taste? I think I'd do proj1/trunk, seems that would be
more isolative of the project. But it's easy enough to change
if you decide it's not the right way to do it.
You would want tags and branches folders in the same position
as the trunk folder I would think.

/Nicke

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 23 13:55:40 2004

This is an archived mail posted to the Subversion Users mailing list.