Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 5 Apr 2002 16:19:36 +0200 From: Christoph Kukulies To: cygwin AT sources DOT redhat DOT com Subject: setup.exe wishlist Message-ID: <20020405161936.B21107@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii I recently upgraded from the b20 full.exe setup mechanism to the newer b20.1 setup.exe. BTW, it looks like a centura team developer application or where does this tree view stem from? At least it requires a bit 'getting used to'. Could please be added that the last used proxy is entered in the registry so it is not required to type in the proxy and port number everytime setup is started. And here I'm already at the next point: Why did I have to run setup so often? 1. sh did not run in the first place since important DLLs (cygintl1.dll) were missing. 2. grep did not run because of some pcre dll missing. 3. gcc compiler was missing, make was missing. All in it took me atleast 10 runs of setup.exe to get everything together. Could the setup have some typical installs, like o minimal (sh, cygwin1.dll, utils) o typical developer (gcc, make, tools) o All Thanks. Nonetheless I like this release much. Many rough edges and glitches like shells in makefiles (/bin/sh: Command not found) have been solved. -- Chris Christoph P. U. Kukulies kukulies AT rwth-aachen DOT de -- 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/