Oh, I think we have a big design problem.
I've seen that we can use relative paths but didn't find a solution with
them as we have a vhost (apache provider) for each repo.
We should have instead 1 vhost for all our repos.
This is not a "breaking things" problem for users as we can add a
general vhost for the externals, waiting for users to smoothly move to
this vhost.
Thank you for the advice. We have work now !
Le 19/07/2010 18:03, Ryan Schmidt a écrit :
On Jul 19, 2010, at 10:38, Bastien Semene wrote:
The doc says that we should not "modify a commit transaction using hook
scripts", but it is possible.
We actually have to change svn:externals values for replication :
- SVNs X1-Y1-... replicate SVNs X-Y-...
- And there are svn:externals between SVN X-Y-...
If we do nothing svn:externals into X1 points to SVN Y instead of SVN Y1.
- Will this modification will break something on the client side, as a user
only see the master or a slave ?
I would expect this would break things, yes.
- Does someone use the pre-revprop-change hook script like this ?
- Is there a cleaner solution ?
Yes, use the relative (instead of absolute) svn:externals syntax.
http://subversion.apache.org/docs/release-notes/1.5.html#externals
--
Bastien Semene
Administrateur Réseau& Système
Cyanide Studio - FRANCE
