> Maybe this is just a matter of how you think about the repository and
> the projects. What follows is (I think) just a clarification of what
> cmpilato just wrote (immutable paths):
>
> 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.
> Set up a tag/ section for the shared libraries, and at appropriately
> stable versions of the library, create a new tagged version.
>
> Then in each of the projects that rely on that library, update the
> svn:external property to point to the new tagged version in the current
> HEAD version.
that would mean to change the property about once a day.
I don't say the job couldn't be done without that feature, but
it's a lot more work than with that feature. And it's also
more likely to produce errors:
A developer changes the library, commits it and forgets
to update the property. The next one to check out
the project won't get the changes to the library.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 24 22:39:38 2003