X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-VirusChecked: Checked X-Env-Sender: mas AT motorola DOT com X-Msg-Ref: server-12.tower-119.messagelabs.com!1213193447!26862985!1 X-StarScan-Version: 5.5.12.14.2; banners=-,-,- Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: Issue with tcltk-20080420-1 (change of behavior from 20060202-1) Date: Wed, 11 Jun 2008 10:10:35 -0400 Message-ID: <573787CA631BFC48879F6EA1E1197A3F02AD480D@de01exm67.ds.mot.com> From: "Schamberger Mark-A11451" To: X-CFilter-Loop: Reflected Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m5BEBHZm025833 I have been using tkdiff (version 4.1.3) with Cygwin for a long time without any problems. After updating the tcltk package from 20060202-1 to 20080420-1, I noticed that tkdiff is no longer working properly when interacting with CVS. The cause of the problem is that when CVS is invoked it is ignoring my CVS_RSH environment variable, trying to use the default rsh instead of ssh to access a remote repository. In the tkdiff.tcl script I changed the command to launch CVS as follows: FROM >> die-unless "exec $cmd update -p $cvsopt \"$f\"" "\"$finfo(pth,$index)\"" TO >> die-unless "exec /usr/bin/env CVS_RSH=ssh $cmd update -p $cvsopt \"$f\"" "\"$finfo(pth,$index)\"" -- thus forcing the CVS_RSH environment variable using the env command. This solves the problem, and tkdiff once again works well with CVS and ssh. I am guessing that in the 20060202-1 version of tcltk, the environment is properly inherited by the exec command, while in 20080420-1 this no longer seems to be the case. Regards, Mark Schamberger -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/