This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Speeding up Cygwin deployment



Yes. You're better off setting up a package server. See:

<http://sources.redhat.com/cygwin-apps/package-server.html>

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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]