Re: svn:externals and revisions

Ian Brockbank wrote:
> We use externals to link in our common code modules to the appropriate
> places in the tree. Linking to tagged revisions is not appropriate for
> us since we need to be at the same point for all platforms/OSes.

By "tagged revisions" are you saying svn:externals defined with a
specific rev? For your purpose, wouldn't it be sufficient to have the
svn:externals point to a branch of the common code base. Then when
tested code was added, the changes would be merged to the branch and all
dependent code would satified.

The problems with that mode are:

1) managing the merges (use SVK, it's much easier);

2) backrevs of dependent project would not get appropriate common code
automatically (this may be a mode your project never uses).

It's this latter issue that the suggested best practices is intended to
deal with: by always using a specific -r option to the svn:externals,
you are guaranteed to get the matching common code. It should be
relatively easy to script a solution which would update the
svn:externals at whatever interval you want in all of the dependent
modules to correspond to the "releases" of the common code base.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org