Eric Kow skreiv, den 26. nov. 2008 16:30: > On Wed, Nov 26, 2008 at 15:18:04 +0000, ÅsmundSkjæveland wrote: >> With both of these options for setting $PATH unavailable, is there any option >> left to get 'darcs push' working again short of writing a patch that lets >> darcs >> store the path to remote-darcs on a per-repo basis? > > If this is possible that some folks have no other means of telling > darcs where the remote darcs lives, (because of sshd configuration, for > example), it would make a lot of sense for us to have a --remote-darcs > flag after all.
I've tested every way I can think of, and I'm very certain that I can no longer set PATH in any way through .bashrc or other init files when doing 'ssh <command>' to my university's linux servers. It annoys me to no end. My workaround will probably have to be to switch to Mercurial, since that system is at the moment installed at the login server, and also supports --remotecmd in the event. Pity, I rather liked darcs. Good luck in the future. > Please see http://bugs.darcs.net/issue223 (which seems to mention the > workaround you tried). It was marked wont-fix to avoid flag > proliferation, but only under the assumption that there was a workaround > for everybody. So I would be happy to see your patch if you were > willing to send it. Sorry, that comment was mostly in jest. I don't know any Haskell, and as much as I'd like to, I can't spare the time to learn a new programming language now. > > Thanks! > > P.S.: >> darcs-devel mailing list (AUTOMATIC POSTINGS ONLY PLEASE!) >> > Please post to darcs-users instead; we have merged our mailing lists Sorry, I missed that bit when I posted through gmane. -- Åsmund Skjæveland _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
