[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: Bob Hiestand <bob.hiestand_at_gmail.com>
Date: 2007-02-26 23:18:23 CET

On 2/8/07, Hendrik Schober <SpamTrap@gmx.de> wrote:

> > [...]
> > Recall that externals can point at different repositories just as
> > easily as they can the same repository. You can't have an atomic
> > commit against more than one repository.
> > [...]
>
> Ugh. What now?
> We'd /really/ like to switch to svn. Hwoever, we would
> need some way to use it so that it fits our needs, not
> the other way around.
> Lemme recap:
>
> We have several projects considerable parts of which
> are shared between them. Developers are hacking away
> on those projects including the shared code, and have
> to check in changes in the shared parts as well as in
> the project-specific parts of the code. When projects
> get tagged, the shared parts should get the same tag.

Hendrik,

  I would personally develop your shared components separately and
rely on your build procedure to pull the correct compiled version.
Treat them as libraries maintained by a third party and enforce a
higher level of change control on them.

  If the above is unpalatable, I would maintain tags and branches
across your entire repository so that everything gets tagged together,
and not use externals at all.

Thank you,

Bob

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 26 23:18:58 2007

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.