RE: Shared source best practices

Nick,

I, too, am curious what other people are doing.

You could have the svn:externals refer to a tag in the common
repository, rather than reference a specific revision of the trunk. That
would provide a similar stability, but then you run the risk of someone
committing changes back to a tag. The latter can be prevented with a
hook script, but it may not be an ideal solution for some.

It seems to me that putting code in separate repositories probably means
that code in each repository should be developed separately, regardless
of how you combine the repositories into working copies using
svn:externals. After all, you cannot commit a change set contains
changes to multiple repositories. IIRC, you cannot even commit a change
set that spans an externals definition boundary, even if only on
repository is involved.

Stuart Celarier | Corillian Corporation

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 31 20:44:21 2006