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

CVS to SVN, best practice

From: Hendrik Schober <SpamTrap_at_gmx.de>
Date: 2007-02-02 16:22:29 CET

Hi,

we consider moving from CVS to SVN. (Mainly because we want to be
able to move and rename files and folders without loosing their
history. The ability to delete old and unused branches also sounds
nice.)
We have a lot of projects in our repository. Many (or even most)
of them share a lot of code. What we do right now is that our
repository is devided into sections:

  *
  |
  +- 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?

TIA,

Schobi

--
SpamTrap@gmx.de is never read
I'm HSchober at gmx dot org
"My hope is that if more people start reading books,
 the world will become a better place."
froarulv in afp
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 2 16:35:54 2007

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