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

Re: Project Organization

From: William Nagel <bill_at_stagelogic.com>
Date: 2004-09-11 00:08:03 CEST

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Bojan,

Why are you considering using multiple repositories? Server
performance or logical separation?

If you are doing it for logical separation, you might consider just
putting the different projects into different top-level directories.
Then, individual developers can checkout just the directory for the
project they're working on, but branching and tagging can easily be
done across multiple projects if desired.

You might also want to look at the svn:externals property, which is
described in fairly high detail in the Subversion book. Using
externals to link a project to other projects may be sufficient for
what you want to do.

- -Bill

On Sep 10, 2004, at 4:52 PM, Bojan Resnik wrote:

> Hello,
>
> I am new to Subversion, having used VSS in the past. I have read the
> Subversion book, and I like the Subversion way of doing things.
>
> However, I am having thoughts about reorganizing the projects, and
> there is a conceptual issue which I cannot seem to resolve. Currently,
> all the projects are in a single VSS database, but it seems to me that
> it would be beneficial if each had its own Subversion repository. The
> problem is that there is set of common projects, and all other
> projects depend on at least one of these. The structure is similar to
> this:
>
> - shared
> - sh1
> - sh2
> ...
> - project1
> - project2
> ...
>
> Both project1 and project2 depend on sh1, while some other
> root-level projects have their own dependencies among the shared
> projects.
>
> Conceptually, it seems that all shared projects should go into one
> repository, and every project into a repository of its own. But,
> Subversion commands work only within a repository, so working with
> this layout would be a maintenance nightmare... Branching for a
> release version would include branching from two repositories, and
> many other tasks would require keeping track of two (or more) revision
> numbers of different repositories... Or maybe I have misunderstood
> something?
>
> Did anyone have similar problems, and what solution did you come up
> with?
>
> Regards,
> Bojan Resnik
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFBQiXDSwe0AHUdEwQRAiSbAKDN64N8RSqTYuuKMz4+GU+1ObiqpACgrMxY
z6ISb/BQ+WVodrv3uE8AloQ=
=Ib93
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 11 00:08:27 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.