Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <3E35BF74.4070009@ece.gatech.edu> Date: Mon, 27 Jan 2003 18:23:32 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "William A. Hoffman" CC: cygwin AT cygwin DOT com Subject: Re: tclsh83.exe should be cygtclsh83.exe References: <5 DOT 2 DOT 0 DOT 9 DOT 0 DOT 20030127112956 DOT 01136520 AT pop DOT nycap DOT rr DOT com> <5 DOT 2 DOT 0 DOT 9 DOT 0 DOT 20030127123246 DOT 03c275d0 AT pop DOT nycap DOT rr DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit William A. Hoffman wrote: > I recently ran setup, and one of the new packages, I think gdb, caused > a tclsh83.exe to be installed into /usr/bin. It would be nice if > this were a full working tclsh83.exe, but it is not. However, it conflicted > with the working tclsh83.exe I already had in my path. Shouldn't the > name of this by cygtclsh83.exe? No. Are you suggesting that all 508 of the .exe's in my /bin should really be named "cyg*.exe"? "cyglynx" "cygman" "cygless" just because they MIGHT conflict with a mingw or native version of less.exe or man.exe? If that is NOT what you are suggestion -- e.g. that only tclsh83 should be renamed -- why? Why is tclsh83 special? It's easy to avoid executable PATH conflicts -- just make sure the tclsh you want appears in the PATH before the one you don't like. End of problem. --Chuck P.S. Now, we *do* name all DLL's with a special 'cyg' prefix, but that is because DLLs are a much more complicated problem than EXEs (memory resident, etc etc) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/