From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1984 invoked by alias); 6 Jan 2009 20:01:46 -0000 Received: (qmail 1877 invoked by uid 22791); 6 Jan 2009 20:01:43 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_73,SPF_PASS X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 06 Jan 2009 20:01:39 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id E30FE60B8018; Tue, 6 Jan 2009 20:01:36 +0000 (GMT) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kbufx7lGT7EE; Tue, 6 Jan 2009 20:01:35 +0000 (GMT) Received: from delenn.bartv.net (hagrid.vpn.ecoscentric.com [192.168.145.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 9A66760B8017; Tue, 6 Jan 2009 20:01:34 +0000 (GMT) Date: Tue, 06 Jan 2009 20:01:00 -0000 Message-Id: From: Bart Veer To: John Dallaway CC: ecos-devel@ecos.sourceware.org In-reply-to: <49639C9C.9040607@dallaway.org.uk> (message from John Dallaway on Tue, 06 Jan 2009 18:02:04 +0000) Subject: Re: #! magic for finding Cygwin Tcl shell References: <49639C9C.9040607@dallaway.org.uk> Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2009-01/txt/msg00010.txt.bz2 >>>>> "John" == John Dallaway writes: John> I was looking at support for UNC file paths in the eCos John> Configuration Tool today. The convoluted #! magic we use in John> our Tcl scripts to find a Cygwin Tcl shell is getting in the John> way when calling (eg) heapgen.tcl via a UNC repository path. John> This code is only needed to support installations of Cygwin John> that are more than 5 years old. John> Rather than increase the complexity of the #! magic still John> further, I think it now makes sense to revert to a simple John> "#! /usr/bin/tclsh" within our Tcl scripts. However, this John> would break compatibility with old Cygwin installations John> providing only tclsh8*.exe or cygtclsh80.exe. John> Any objections? There is another approach we could consider. Instead of invoking "tclsh", we could invoke "ecosconfig tclsh". That would require a minor change to ecosconfig. Combine that with a statically linked build of ecosconfig, and we should end up with something much more robust than the current approach of depending on whatever version of Tcl happens to be installed, somewhere, under some name or other. However, any changes along those lines should probably wait until after the 3.0 release. AFAIK, what we have right now seems to work well enough. Bart -- Bart Veer eCos Configuration Architect eCosCentric Limited The eCos experts http://www.ecoscentric.com/ Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071.