As suggested in issue1025, an alternative solution would be to have a
'local_darcs' preference in the remote repository telling anyone interacting
with that repo how to call darcs on this machine.

This way, if on my machine I have darcs installed in /some/funky/path/darcs-sfx,
I can just set local_darcs to that path. Anyone pushing to my repository will
execute this command.

If flag proliferation is a problem, instead of a flag, include it in the url
scheme, like so: 'darcs push toto@machine:/repo#darcs-command'. This way, it can
be saved in the repos file, and persist between session.

This just came up again in issue1025.  Since there is a decent workaround for
this, I'm leaving it as wont-fix, to avoid flag proliferation.

That said, it may be worth considering.  Maybe this sort of flexibility would be
useful anyway (do we want to make it convenient for people to "try out" other
darcses on the server?), and besides, we now have a notion of advanced flags to
mitigate the ill effects of flag explosion.

Somebody should just submit a patch and see what David thinks :-)

Not needed.  See http://thread.gmane.org/gmane.comp.version-control.darcs.user/10991

Note that I when I made this request, I had not realised you could use edit your
.bash_profile or .cshrc on the remote end and it would find the right darcs. 
Not sure if --remotedarcs is all that useful then...

This sounds reasonable.
-- 
David Roundy

What might be handy for darcs push on remote servers where darcs is not
installed in the expected places, for example,
  darcs push --remotedarcs="/opt/local/bin/darcs"

Files affected: RemoteApply.lhs, DarcsFlags.lhs and DarcsArguments.lhs
I think.