Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 29 Jan 2002 12:26:56 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Scripting Installs? Message-ID: <20020129172656.GE641@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <5.1.0.14.0.20020129114033.00b1f148@mail.corp.lumeta.com> <5.1.0.14.0.20020129114033.00b1f148@mail.corp.lumeta.com> <5.1.0.14.0.20020129120453.022a5068@mail.corp.lumeta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.0.20020129120453.022a5068@mail.corp.lumeta.com> User-Agent: Mutt/1.3.23.1i On Tue, Jan 29, 2002 at 12:07:44PM -0500, Glenn Sieb wrote: >On 11:58 AM 1/29/2002 -0500, Christopher Faylor wrote: >>There is no way currently to avoid having setup.exe access the cygwin >>site for updates to setup.ini, if that is what the user asks it to do. >>The primary purpose of setup.exe is to install a complete cygwin >>distribution. I don't really see any reason to change this behavior but >>you can certainly modify setup to fit your needs. > >Well 39 meg to run ssh is a bit much, even by Windows-standards (grin), And, I should care about your specific requirements because... cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/