Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Subject: Re: cygwin-apps Digest 2 Nov 2001 18:46:34 -0000 Issue 223 From: Robert Collins To: cygwin-apps AT cygwin DOT com In-Reply-To: <20011103120128.C18219@redhat.com> References: <20011103052046 DOT 46423 DOT qmail AT web20008 DOT mail DOT yahoo DOT com> <1004786864 DOT 1816 DOT 13 DOT camel AT lifelesswks> <20011103120128 DOT C18219 AT redhat DOT com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.15 (Preview Release) Date: 04 Nov 2001 11:06:50 +1100 Message-Id: <1004832411.4741.8.camel@lifelesswks> Mime-Version: 1.0 X-OriginalArrivalTime: 04 Nov 2001 00:11:08.0054 (UTC) FILETIME=[339FF360:01C164C5] On Sun, 2001-11-04 at 04:01, Christopher Faylor wrote: > On Sat, Nov 03, 2001 at 10:27:43PM +1100, Robert Collins wrote: > > Actually, IMO, what the above means is that cygwin.bat should not > be created if bash.exe is not installed. There is no requirement > that cygwin.bat should always be created. It makes no sense to > do so if you have not downloaded the correct components. Good point. So cygwin.bat should actually be part of the bash package, with a post install script to tweak it as setup.exe currently does. Who wants to contribute the script? Rob