This patch allows to specify the name of the darcs executable on the server side,
but currently only for push, not transfer mode. For the latter, we are missing the
neccessary information on network flags. But at least for push it seems to work
and makes things easier.
Using an environment variables (eg, $DARCS_REMOTE) would be easier, but is propably
not consistent with the rest of the darcs UI.

Wed Nov 18 16:56:49 CET 2009  Benedikt Huber 
  * resolve issue223, add --remote-darcs flag for remote darcs executable
  This patch adds a flag '--remote-darcs COMMAND' to specify the name of the darcs
  executable on the remote end. Unfortunately it currently only works for remote apply,
  not for the transfer mode optimization. The problem: SSH transfers are used at many
  points in darcs (eg, HashedIO), where transfer flags are not available.
  The relevant starting points for fixing this are '[gz]fetchFilePS' in External.hs.

Attachments

• resolve-issue223_-add-__remote_darcs-flag-for-remote-darcs-executable.dpatch
• unnamed

This patch bundle (with 1 patch), which can be  applied to the repository http://darcs.net/ is now tracked  on DarcsWatch at http://darcswatch.nomeata.de/repo_http:__darcs.net_.html

This patch bundle (with 1 patches) was just applied to the repository http://darcs.net/.
This message was brought to you by DarcsWatch
http://darcswatch.nomeata.de/repo_http:__darcs.net_.html

This patch bundle (with 1 patches) was just applied to the repository http://darcs.net/reviewed.
This message was brought to you by DarcsWatch
http://darcswatch.nomeata.de/repo_http:__darcs.net_reviewed.html#bundle-fdedc82f67dd5fedd9321e048c219e2908fb3234