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

Re: svn:externals

From: Ben Gollmer <ben_at_jatosoft.com>
Date: 2003-04-25 00:03:52 CEST

On Thu, 24 Apr 2003 15:37:32 -0500, SteveKing <steveking@gmx.ch> wrote:
> > Instead of trying to automatically load your libraries in
> > "svn:external", how about linking specific tagged versions?
> That's not what we need. We have one project (a library) which
> is used from several other projects. This library evolves with
> those other projects. So during development on the projects
> themselves the library also changes. And the changes to the
> library get committed with every commit to the project.

My quick thoughts on this problem: The simple (relatively speaking) solution
seems to be a hook in svn copy that will look at the svn:externals property on
the directory being copied, check the revision # of each external lib, then fix
up the svn:externals property to include the revision number before committing.

Of course, there could be a switch to turn this automatic update on/off, in case
you wanted your copy to continue tracking the trunk of the external lib(s).

This isn't exactly the same as CVS - as Ben Collins-Sussman brought up on IRC,
it doesn't quite work out for branches. CVS users would expect external libs to
automatically branch when they create a main project branch.

If you are using your copy as a tag, however, it works out fine. Personally,
since I have very little prior experience with CVS, I wouldn't expect automatic
branching of external libs anyway.

Thoughts? Would libsvn_client/copy.c be the place to implement this?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 25 00:04:51 2003

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

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