[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Propagating changes from one repository to another

From: Marc Haisenko <haisenko_at_comdasys.com>
Date: 2006-07-31 17:26:59 CEST

Hi folks,
we're faced with a tricky problem, and before I start writing my own solution
I'd like to know whether someone already has a solution.

We'll license software from us to a customer. The customer will get a
SubVersion repository with our software, minus some files/directories.

Yes, the customer has to have a separate repository, for several reasons.

Now part of the contract is that we have to provide updates to the customers
version. So we have to push changes from our repository to theirs.

I know already that there's SVN::Pusher, but it doesn't do the job,
unfortunately: it already chokes on a missing directory on the customers

I fear that there's nothing readily available which will aid me, is there ?

My solution would be "advanced diff" and "advanced patch" which parse "svn
log" output on the master side (to detect deletes/renames/copies/property
changes) and translate them to the according actions on the slave side, with
error handling (there will be conflicts when the client starts editing his
version, there will be files missing on the slave side, and it doesn't have
to run fully automatic). Does something in that direction already exist ?


Marc Haisenko
Comdasys AG
Rüdesheimer Straße 7
D-80686 München
Tel:   +49 (0)89 - 548 43 33 0
Fax:   +49 (0)89 - 548 43 33 29
e-mail: haisenko@comdasys.com
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 31 17:28:32 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.