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 |
Message-ID: | <000701c20225$06c2f240$0610a8c0@wyw> |
From: | "Wu Yongwei" <adah AT netstd DOT com> |
To: | <cygwin AT cygwin DOT com> |
Subject: | An updated 2.125 setup possible? |
Date: | Thu, 23 May 2002 14:42:35 +0800 |
MIME-Version: | 1.0 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.50.4910.0300 |
Is it possible to maintain a 2.125 setup? If I am not mistaken, the only current problem is the MD5 checksum in the ini file. We need only to make the 2.125 setup ignore them. The "new" setup should be ideally put in the directory containing setup.exe and be named setup-old.exe. Maybe it is an unwelcome bad idea but the new setup really frets me. I would love to do the above myself if I were able to do it in an hour. But it seems I am really not familar enough with the GNU configuration and Cygwin code itself. Best regards, Wu Yongwei -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |