delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Date: | Thu, 26 Feb 2004 18:32:58 -0600 |
From: | Charles Plager <cplager+cygwin AT physics DOT ucla DOT edu> |
Subject: | Request: Cgywin version dependancy listed in setup |
To: | Cygwin Mailing list <cygwin AT cygwin DOT com> |
Message-id: | <403E903A.7060800@physics.ucla.edu> |
MIME-version: | 1.0 |
User-Agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 |
Hello, I don't know if this has been discussed before or not (my apologies if I missed it). It seems clear to me that not everybody always wants to upgrade to the latest version of the cygwin dll. The problem comes when we do want to upgrade one particular piece of cygwin. As far as I can tell, it is really hard to tell whether a new piece of software requires a newer version of the cygwin dll that you have installed or whether it will work fine. (Not that I have to ask, but) Any thoughts, comments? Thanks, Charles -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |