On Jul 31, 2006, at 17:26, Marc Haisenko wrote:
> 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 ?
svn_load_dirs.pl may be a solution; you could package up new releases
by exporting from your repository and tarring and zipping it up, and
they could load it into their repository with this script.
http://svnbook.red-bean.com/en/1.2/
svn.advanced.vendorbr.html#svn.advanced.vendorbr.svn_load_dirs
svk may be another solution, though I'm not sure if it's designed for
this purpose.
http://svk.elixus.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 31 20:17:25 2006