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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 31 Jan 2002 10:29:39 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Scripting Installs? missing setup.hints Message-ID: <20020131152939.GA7966@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <0ba101c1a999$b639db60$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Thu, Jan 31, 2002 at 09:28:31AM -0500, Michael Adler wrote: >On Thu, 31 Jan 2002, Robert Collins wrote: > >> Create a setup.ini on a local web server describing your software. Read >> http://www.cygwin.com/setup.html. Add the appropriate requires: line to >> your local setup, which will drag in the needed packages from the normal >> cygwin mirror sites. > >I'm trying something slightly different. I have a mirror of all the >packages so that installs are over the LAN. I want to generate a setup.ini >for all those packages, but it looks like there are many missing >setup.hints. Is this on purpose? The information is in the setup.ini file. Eventually all info will be moved to setup.hints. >Is this the responsibility of the package maintainers? Yes. If they feel like doing so. >How is the central setup.ini generated? With a perl script. >How could one roll their own? By writing a program. >Thanks for your support. Let's get them hooked on those snazzy GNU apps! Uh huh. 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/