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

Re: mantaining a shared library in subversion

From: Phil Endecott <spam_from_subversion_users_at_chezphil.org>
Date: 2006-01-23 01:36:31 CET

Manuel López-Ibáñez wrote:
> I wish to maintain a library which will be shared by several projects
> which are close related to each other and thus will share the same
> repository.

> In order to connect each project to a copy of the library using
> externals definitions, I would create a directory for each project and
> set svn:externals to point to library/trunk.

> 2) Tagging.

See also the "svncopy" script from the contrib directory. It does
something similar to "svn cp", but will modify external definitions
while copying in suitable ways for tagging and branching.

> From the mails found on the mailing list [2][3], I got the impression
> that external definitions are not very well-suited to maintain a shared
> library within the same repository.

It's not perfect, but many of us are using something similar to what
you've described and it does work.

> Therefore, I would choose a mix of working copies as the best way to
> handle this scenario.

I made the other choice.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 23 01:37:49 2006

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.