Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: RE: Setup.exe release-candidate X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Sat, 16 Mar 2002 01:01:00 +1100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Setup.exe release-candidate Thread-Index: AcHMKOXlU7ZoPFkMS+S5WOfG5eSeyQAABKyQ From: "Robert Collins" To: , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2FE2A102447 > -----Original Message----- > From: fergus@bonhard.uklinux.net [mailto:fergus@bonhard.uklinux.net] > Sent: Saturday, March 16, 2002 12:54 AM > If those of > us who need to keep a local copy of the current setup.exe > v.2.125.2.10, is there any reason why it shouldn't work with > future setup.ini's, even after [if] you release this version > v.2.194.2.11, or something close to it, as standard? Fergus Yes. Firstly, there are plans to move functionality out of setup.exe into packages where it can be more easily maintained. This includes things like /etc/passwd creations, /etc/profile creation.. you get the drift. Secondly not all enhancements and extensions to setup.ini and the package format will be backwards compatible. Given that this is a volunteer operation, I can *guarantee* that we won't be jumping through hoops to retain backwards compatability. We will likely have staggered changes - i.e. introduce the capability a revision before the change occurs - but that won't help you... If you are able to run gdb, you are able to help me debug this though. So, if you'd like to be able to move with the rest of us.... 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/