CVS/Root should record the CVS_RSH environment value...
It is _VERY_ unfortunate that CVS/Root does not record the setting of CVS_RSH. $ cvs -t status Makefile - main loop with [EMAIL PROTECTED]:/cvs - Starting server: rsh anoncvs.comstyle.com -l anoncvs cvs server ^?cvs [status aborted]: received interrupt signal ksh: exit code: 1 $ CVS_RSH=ssh cvs -t status Makefile - main loop with [EMAIL PROTECTED]:/cvs - Starting server: ssh anoncvs.comstyle.com -l anoncvs cvs server === File: Makefile Status: Up-to-date Working revision:1.89 Repository revision: 1.89/cvs/src/Makefile,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) Gr -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS/Root should record the CVS_RSH environment value...
On Tue, 4 Feb 2003, Greg A. Woods wrote: Date: Tue, 4 Feb 2003 14:19:34 -0500 (EST) From: Greg A. Woods [EMAIL PROTECTED] Reply-To: CVS-II Discussion Mailing List [EMAIL PROTECTED] To: CVS-II Discussion Mailing List [EMAIL PROTECTED] Subject: CVS/Root should record the CVS_RSH environment value... It is _VERY_ unfortunate that CVS/Root does not record the setting of CVS_RSH. What's unfortunate is that the repository identification syntax does not experss the protocol, so you have to use the CVS_RSH hack to do so, relying on command compatibility of ssh and rsh. Then the purpose of CSV_RSH would be relegated to selecting an alternate rsh implementation, not to switch to a different rsh-compatible transport. An extension along the lines: :ext-rsh:user@host:/path/to/repo :ext-ssh:user@host:/path/to/repo could be the thing. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS/Root should record the CVS_RSH environment value...
[ On Tuesday, February 4, 2003 at 12:35:03 (-0800), Kaz Kylheku wrote: ] Subject: Re: CVS/Root should record the CVS_RSH environment value... What's unfortunate is that the repository identification syntax does not experss the protocol, so you have to use the CVS_RSH hack to do so, relying on command compatibility of ssh and rsh. No, that's not the prolem. The _protocol_ in both instances is identical from CVS' point of view. All we're changing is the tool used to invoke the remote execution. This tool's name should be recorded along with the the $CVSROOT information since these two pieces of information undoutably go hand-in-hand. An extension along the lines: :ext-rsh:user@host:/path/to/repo :ext-ssh:user@host:/path/to/repo could be the thing. That could solve the problem as well, but seems to me to be the wrong approach -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVS/Root should record the CVS_RSH environment value...
Greg Woods wrote: An extension along the lines: :ext-rsh:user@host:/path/to/repo That could solve the problem as well, but seems to me to be the wrong approach Indeed, it's not general enough. I wonder if it's not better to have a single file under the CVS subdirectory that encapsulates all the environmental info needed for cvs to operate on that work area. Something like CVS/Environment, containing: CVSROOT=... # why have a separate Root and Repository file? CVS_RSH=... # anything else Or any of these entries could be split up enough to make external text processing easier (like Root and Repository are separated these days). -- Shankar. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
