X-Spam-Check-By: sourceware.org Message-ID: <451763A7.3060502@princeton.edu> Date: Mon, 25 Sep 2006 01:05:43 -0400 From: Vinod Gupta User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Speeding up Cygwin deployment Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 > Yes. You're better off setting up a package server. See: > > > > From this you can control the packages installed but can use 'setup.exe' to > install, which understands how to unpack packages, symlinks, and run > postinstall scripts. Also, you'll have a server from which to roll out any > updates conveniently. > > -- > Larry Hall http://www.rfk.com I was looking at the Cygwin installation FAQs, which says that "setup.exe" method can not run in unattended mode. For the same reason, WinXP's builtin zipper can not be scripted either. Using info-zip's stand-alone binaries zip.exe+unzip.exe are perfect for my purpose except the presence of files like atobm.1.html which are not visible to info-zip or any DOS application. Why Cygwin need to create these types of files while the files like allec.1 serve better i.e seen as symlink by cygwin, as shortcut by Windows, also visible to DOS apps. Presence of atobm.1.html like files makes WinXP's builtin unzipper crawl to its knees. What kind of files are these? Vinod -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/