Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Sun, 27 May 2001 22:02:12 EDT To: cygwin AT cygwin DOT com Subject: Re: Setup.exe v2.56 X-Mailer: Virtual Access by Atlantic Coast PLC, http://www.atlantic-coast.com/va Message-Id: From: Brian Keener Reply-To: bkeener AT thesoftwaresource DOT com In-Reply-To: <001d01c0e70e$c2eacca0$562fa4cb@brasd1.vic.optushome.com.au> References: <20010527031018 DOT A14119 AT redhat DOT com> <00af01c0e680$0afc8ea0$562fa4cb AT brasd1 DOT vic DOT optushome DOT com DOT au> <001d01c0e70e$c2eacca0$562fa4cb AT brasd1 DOT vic DOT optushome DOT com DOT au> Travis Howell wrote: > The previous version of Cygwin setup didn't have this limitation, is there > any chance or adding back support for it ? Ummm, How long ago are you talking about - Most of the setups I have worked with since this new version (GUI) began (I believe) have used the method of the subdirectories and the setup.ini. When you use setup to download the files it automatically keeps a copy of the setup.ini file for you. > The main reason I ask is using the above method allows setup to easy manage > installation and uninstallation of any Cygwin binary tarballs, including This can still be done I believe - Create the subdirectory under your downloaded files directory and place the appropriate tarball there and modify your local copy of setup.ini to have an entry for the package you want to install with the appropriate directory entry and other flags you see in the setup.ini. bk -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple