Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Wed, 21 Mar 2001 11:12:49 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Cc: cygwin-apps AT cygwin DOT com Subject: setup wishes -- any volunteers Message-ID: <20010321111249.A5850@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com, cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com, cygwin-apps AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i It would be "real nice" (tm) if setup could be modified to do too things: 1) Understand simple dependencies (relatively easy?): If you download gcc, you need cygwin and w32api. If you download bash, you need cygwin. 2) Have some way of viewing categories of files: Source Code development: gcc The GNU Compiler Collection binutils The Linker, Assembler and other tools gdb The GNU debugger Shells bash The Bourne Again Shell tcsh The C Shell etc. I think that both of these would make setup.exe much more useful to the first time installer. Probably we could then stop the "download everything" default that is going to become more unmanageable as the distribution grows. Any volunteers? I'd love to do this myself but I really don't have the time. (tm) Or, hmm. Maybe I don't understand the Windows API well enough to do this? (tm) cgf