Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com From: Shankar Unni Subject: Re: cygwin 1.5.10: Possible bug Date: Tue, 22 Jun 2004 10:09:10 -0700 Lines: 17 Message-ID: References: <40D6C0D8.8070207@phenix.fr> <20040621203006.GA8404@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: adsl-68-120-146-125.dsl.snfc21.pacbell.net User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 Thunderbird/0.7 Mnenhy/0.6.0.101 In-Reply-To: <20040621203006.GA8404@trixie.casa.cgf.cx> Christopher Faylor wrote: > So, if anyone is under the impression that this is just a > lack of time, that is not the case, at least for me, and, I suspect that > Corinna is in the same boat. Agreed. This is basically a special-purpose issue, so the onus is on us to figure out what can be done. The times it has come up to bite the average user are few and far in between. In particular, the tcl/tk fiasco is the only one that has bitten a significant number of people, and mostly because the Cygwin tcl package doesn't follow the Cygwin convention of prefixing the DLL names with "cyg" (i.e. instead of "cygtcl84.dll", it's just "tcl84.dll", and it ends up getting picked up by programs that try to dynamically load a TCL scripting engine). So anyway, to cut a long story short, I agree with cgf :-). -- 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/