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: Mon, 28 May 2001 00:00: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: <002e01c0e71b$39b57360$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 last released Cygwin setup version (2.29) works fine without sub > directories or setup.ini. Well, alrighty then - my mistake. I've been working on these other versions for so long - sort of loose touch. Then Back to your original question - I suppose it would be possible to put that functionality back although I will leave it to others to discuss whether that is setups function to install packages that it has no knowledge of or not. I do know all enhancements and patches are gratefully accepted - they even take them from me. :-) > But won't that changes be overwriten each time setup.ini is updated on Cygwn > FTP sites ? Each time you do a Download from Internet or an Install from Internet - yes. Obviously an Install from local directory would not. If you copy the downloaded files and their respective directories/subdirectories in total along with the setup.ini to a new source point (which is sort of what I thought you were doing) and keep all your setup.ini changes at the beginning or the end of the file - then it should be easy cut and paste but it is something most people would get tired of remembering to do. bk -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple