RE: repository layout for two projects and multiple libraries

Another option you don't mention, I've been toying with using a separate
repository* for the libraries and using svn:external to reference them
from each project.

I think you do need to make 'releases' of the libraries, but they simply
follow the union of the projects' release schedules - each project
release takes a snapshot of the libraries at the time.

To pin the project development to a particular library version, you
change the svn:external reference to point to the appropriate branch.

The only hassle here is deciding where a project's modifications to a
branch should go .. They'll end up in the library's repository/tree, not
the projects. If this is a problem, then you need to deal with the
libraries like third-party with their own release schedule

Make sense? I haven't nailed this one myself yet, I'm fishing for ideas
as much as anyone.

- Walter

* Note, you don't need to use a separate repository if you don't want
to.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 17 21:30:01 2003