Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 31 Jan 2002 11:22:36 -0500 (EST)
From:	Michael Adler <adler AT glimpser DOT org>
To:	Christopher Faylor <cgf AT redhat DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Scripting Installs? missing setup.hints
In-Reply-To:	<20020131152939.GA7966@redhat.com>
Message-ID:	<Pine.NEB.4.44.0201311110330.19886-100000@reva.sixgirls.org>
MIME-Version:	1.0

> 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.

If I create them, would you incorporate them?

> >How is the central setup.ini generated?
>
> With a perl script.

Fascinating. Is it in the CVS? It's not jumping out at me.

> >How could one roll their own?
>
> By writing a program.

That much I've figured out, but I appreciate these helpful suggestions.

The missing part was how to generate setup.ini without all the
setup.hints. I knew that you had to do it somehow, but I can't find it in
the CVS. So, should I chop up your setup.ini and give it back to you as
setup.hints (or just use locally)? or is your current solution better and
shareable?

Thanks,

Mike Adler




--
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/

- Raw text -