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 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: environment variables and setup.exe X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Sat, 4 May 2002 09:23:37 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "John Vincent" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g43NO4W13933 > -----Original Message----- > From: John Vincent [mailto:jpv50@hotmail.com] > Sent: Saturday, May 04, 2002 1:55 AM > To: cygwin@cygwin.com > Subject: environment variables and setup.exe > > > May I suggest that the setup.exe program examines > the PATH and CYGWIN environment variables and > offers to set them to values that allow the postinstall > scripts to work on a system that has not had any cygwin > binaries installed before. Its especially confusing to find > that cygwin1.dll is not on the path after selecting "Installation". Setup runs the post install scripts via the cygwin batch file that sets the path - or it's meant to. As for setting the path to allow running cygwin commands from a command prompt (for example), patches gratefully accepted. Can I suggest that a post-install script for cygwin1.dll is the appopriate place to put this though. 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/