X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Shankar Unni Subject: Why does tcl84.dll not follow the Cygwin DLL naming convention? Date: Tue, 25 Jul 2006 10:07:32 -0700 Lines: 17 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.3.0 X-IsSubscribed: yes 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 I notice that the Tcl/Tk libraries are the only DLLs (*) in Cygwin's /usr/bin that don't follow the "cygwin DLL naming convention" of prefixing "cyg" to the DLL name. (The issue that prompts this idle speculation is described in these postings: http://sourceware.org/ml/cygwin/2004-02/msg00195.html http://sourceware.org/ml/cygwin/2004-02/msg00071.html ) This just a casual question: why? I know, WJM and all that, but why don't these libraries have a "cyg" prefix - which would solve all these problems? And I suppose it's too late to fix this now, even if it could be? I guess it would require re-releasing several packages that depend on it.. -- 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/