Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com content-class: urn:content-classes:message Subject: cinstall location MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 26 Apr 2002 01:32:08 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Cygwin-Apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3PFWCV23364 Chris, sometime ago in a conversation about cinstall and the all-in-one setup the topic of cinstall's location was rasied. At that point I didn't see any need to move cinstall.... but I'd actually like to see it moved to the cygwin-apps repository now. Why? So that we can add a build dependency on a mingw libstdc++, and be done with reinventing multiple wheels. I think that while moving won't be trauma-less, it will result in more rapid development, and that can only be a good thing. It will also make having a cinstall -src tarball easier, and the cygwin src snapshots smaller. It's not intended to lessen the link between cinstall and cygwin at all, rather to make building it easier. What do you think? Rob