From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27934 invoked by alias); 26 May 2002 22:02:38 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 27927 invoked from network); 26 May 2002 22:02:37 -0000 Received: from unknown (HELO itdomain003.itdomain.net.au) (203.63.157.208) by sources.redhat.com with SMTP; 26 May 2002 22:02:37 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Setup as recommended reading X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Date: Mon, 27 May 2002 02:01:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Nicholas Wourms" , X-SW-Source: 2002-05/txt/msg01617.txt.bz2 > -----Original Message----- > From: Nicholas Wourms [mailto:nwourms@yahoo.com]=20 > Sent: Monday, May 27, 2002 5:12 AM > To: Robert Collins; cygwin@cygwin.com > Subject: RE: Setup as recommended reading >=20 >=20 > Hi, >=20 > Before you do bow out, I think people need to realize, as it=20 > was stated before, that you are not trying to reinvent the=20 > wheel. Yes, RPM is great for many things, but the goal of=20 > setup isn't to be rpm. In fact, IIRC it was stated that once=20 > someone had volunteered to support rpm for Cygwin and it was=20 > proved stable, there might be some discussion as to making=20 > setup.exe based on the rpm api. There has been some=20 > discussion lately regarding this port and I believe someone=20 > has even volunteered to do it.=20 Yes. In fact both rpm and have been -partially- ported to cygwin. AFAIK neither has been converted to deal with in-use-file-replacements, which is a required capability to be a cygwin-linked installer (for somewhat obvious reasons). > Be that as it may, it will still be much time before this is=20 > implimented, IF it is implemented. So let Rob actually=20 > perfect what he has before asking for heaps of new features.=20=20 > IMHO, setup seems to be working nicely for the most part,=20 > minus a few bugs here and there. I honestly think there are=20 > more critical issues to focus on then the "fluff" of UI, such=20 > as getting a fast, stable SysV IPC system integrated into=20 > cygwin and releasing an updated binutils with better dynamic=20 > library capabilities.=20 > Feel free to disagree.... The installer is fairly complete. Howeever I really want to make it easy for maintainers, so allowing the use of the debian build tools, or the rpm build tools is a high priority. Otherwise the maintainers here will, by necessity, end up inventing the wheel. 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/