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 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: An updated 2.125 setup possible? X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Date: Thu, 23 May 2002 19:44:35 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Wu Yongwei" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4N9jS405535 > -----Original Message----- > From: Wu Yongwei [mailto:adah AT netstd DOT com] > Sent: Thursday, May 23, 2002 4:43 PM > To: cygwin AT cygwin DOT com > Subject: An updated 2.125 setup possible? > > > 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. And source only packages. And postinstall scripts. You are welcome to maintain a fork that supports these features. I don't have time to do so myself. Or... you could contribute towards making the newer setup meet your needs better. Rob -- 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/