Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: RE: missing telnet, solution Date: Tue, 26 Mar 2002 10:56:56 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message X-MS-TNEF-Correlator: From: "Robert Collins" To: "mstucky5" , "Cygwin@Cygwin.Com" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2PNvYh19274 > -----Original Message----- > From: mstucky5 [mailto:mstucky5@cox.net] > Sent: Tuesday, March 26, 2002 10:10 AM > To: Cygwin@Cygwin.Com; cygwin-xfree@cygwin.com > Subject: Re: missing telnet, solution > > > This whole thread got me thinking about possible ways > to avoid this "xxx is missing" problem... > > I thought that I'd throw an idea out for discussion... > > Would it make sense to have setup install a dummy > script for some of the common utilities and then > overwrite that script with the actual utility if > it is selected from the gui as it should be? In debian, there is a package that will do this - I think it that when a binary is not found it queries dpkg to see if a package that can provide it exists. Anyway, I think that an _automated_ approach to this could be quite useful, but not a manual one. (I realise that you didn't imply either, I'm simply getting there first :}). 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/