darcs

Issue 1025 --remote-darcs=COMMAND flag for when darcs executable has a non-standard name

Title --remote-darcs=COMMAND flag for when darcs executable has a non-standard name
Priority feature Status duplicate
Superseder add a --remote-darcs flag
View: 223
Nosy List beschmi, dagit, galbolle, jaredj, kowey
Assigned To Topics ProbablyEasy, SSH, UI

Created on 2008-08-21.21:32:11 by galbolle, last changed 2008-08-23.07:21:33 by kowey.

Messages (mbox)
msg5627 (view) Author: galbolle Date: 2008-08-21.21:32:02
Interacting with a server on which the darcs executable is not named darcs (but,
say darcs-2.0.2 or whatever) is painful. Some ideas to relieve the pain:

Commands interacting with a remote darcs executable should accept a
--remote-darcs=COMMAND flag. When they are invoked with this flag, they exec
COMMAND instead of darcs on the remote host.

Symetrically, there could be a local_darcs pref telling remote darcs to use a
given command instead of 'darcs' when trying to invoke darcs ot that host.
msg5661 (view) Author: kowey Date: 2008-08-23.07:21:26
Duplicate of issue223, discussion there.

Browse related patches: unstable | stable

History
Date User Action Args
2008-08-21 21:32:11galbollecreate
2008-08-23 07:21:33koweysetstatus: unread -> duplicate
nosy: beschmi, kowey, dagit, jaredj, galbolle
superseder: + add a --remote-darcs flag
messages: + msg5661