Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <40D9A8F7.1030202@etr-usa.com> Date: Wed, 23 Jun 2004 09:59:51 -0600 From: Warren Young User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 MIME-Version: 1.0 To: Cygwin-L Subject: Re: cygwin installer References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Jonah Bossewitch wrote: > > some documentation for creating a standalone windows installer Another way that hasn't been mentioned is to: 1) Run setup.exe to download all the packages you need. Get it all working and tested. 2a) (Simple path.) Next, put the setup.exe and the download tree that was created on a central file share. Then tell your students to run setup.exe from there and tell it to do a Local install and don't change anything. Just say "Next" all the way through. You might need to fiddle with setup.ini to make sure the packages you need default to being installed. 2b) (Harder.) If you really need it to be totally prompt-less, there was a proposal once to add command line flags to setup.exe to make it more automatable. You could be the one to finally implement that idea. Once that is done, there are a bunch of ways you can use it, ranging from a simple DOS batch file to run setup.exe with the right flags, to using one of the various Windows installer tools to pack the whole mess up into a single EXE file and run setup.exe with the right flags. Beware that if you're going to distribute binaries in this way, you will also have to distribute the corresponding sources. -- 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/