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

Re: CVS to SVN, best practice

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-02-02 18:32:04 CET

On 2/2/07, Hendrik Schober <SpamTrap@gmx.de> wrote:
> *
> |
> +- 3rdparty
> | |
> | +- 3rdparty1
> | |
> | +- 3rdparty2
> |
> +- projects
> | |
> | +- project1
> | |
> | +- project2
> |
> +- shared
> |
> +- shared1
> |
> +- shared2
> If I need to work on project1, I check it out and execute a
> script in its root folder, which checks out/exports all necessary
> 3rd-party and shared code. Tagging the checked out stuff will tag
> all (checked out) 3rd-party and shared code, too. The same goes
> for branching.
> How could we do the same using SVN? I understand that it is a
> convention to have "branches", "tags", and "trunk" folders in your
> repository. Is this, by convention, in the repository's root? So
> when I tag, do I then tag the whole repository?
> How do you handle this?

I keep my tags at the project level, so that I have the following:

And so on. Tagging the whole repository would just add clutter IMHO.
The idea is that if I look at \Project1, the whole history of that
project is right there - tags, branches, trunk, everything. If tags
were at the same level as Project1 (right off the root), I'd have to
look in multiple places to get that same information.

It sounds like you need a combination of externals (to pull everything
required to work on a project into one checkout) and a script to help
tagging (so that the externals in your tags point at the appropriate
revisions of those externals, and (it sounds like) create a tag for
those external elements as well).

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 2 18:32:34 2007

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