> -----Original Message-----
> From: Henrik Sundberg [mailto:storangen@gmail.com]
>
> 2007/6/14, "schönfeld / in-medias-res.com"
> <schoenfeld@in-medias-res.com>:
> > Subversion talks about two variants of providing
> repositories. One per
> > project, or one for several projects. I would like to use the first
> > variant, but i anyway need a way to be flexible with this.
> What I am
> > asking for, is if there is a solution for my dillema, or not.
>
> In my (novice) opinion, it is a matter of what you actually
> need. E.g. if you have the structure: repos/
> proj1/
> branches/
> tags/
> trunk/
> proj2/
> branches/
> tags/
> trunk/
>
> Is it really important to distinguish proj1 and proj2 as
> separate repositories, or could they just be directories in
> one repository?
>
> /$
>
Maybe, and yes. It depends on what you need to do.
Subversion tracks the revision number of the repository, and it doesn't
assign "version numbers" to individual files. You can choose to make
projects as directories in one repository. If you do, then a change to any
project will increment the revision numbers that every project sees. This
can be confusing.
It might be important for you to account for every change to a project, that
is, something like:
Revision 100 made these changes, revision 101 made these others, and so
forth. If all your projects are in one repository, you will have gaps in
that revision count, and your customer/manager/build engineer/auditor/etc.
might not like that.
You might also find it easier to manage and backup several smaller
repositories rather than one large one.
Hope this helps!
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 19 21:44:28 2007