----- Original Message -----
From: "Marc Haisenko" <haisenko@comdasys.com>
To: <users@subversion.tigris.org>
Sent: Monday, July 31, 2006 11:26 AM
Subject: Propagating changes from one repository to another
> 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
> side.
>
> 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 ?
Have the customer dedicate tags to a local copy of your software, updating
tags or branches from it when you send them new tarballs or patches. That
makes integrating their modifications a local problem, not yours, and lets
them have clean reference tags to your software for local comparision.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 1 10:56:41 2006