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 13:45:06 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Scripting Installs? missing setup.hints
Message-ID: <20020131184506.GE7966@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20020131152939 DOT GA7966 AT redhat DOT com> <Pine DOT NEB DOT 4 DOT 44 DOT 0201311110330 DOT 19886-100000 AT reva DOT sixgirls DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.NEB.4.44.0201311110330.19886-100000@reva.sixgirls.org>
User-Agent: Mutt/1.3.23.1i


[It's not necessary to Cc me.  That's why I set the Reply-To.  I am
reading the cygwin AT cygwin DOT com mailing list: http://cygwin.com/bugs.html
]

On Thu, Jan 31, 2002 at 11:22:36AM -0500, Michael Adler wrote:
>
>> 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?

Sorry, no.  That's up to the maintainers.  There is no strong need to do this.

>> >How is the central setup.ini generated?
>>
>> With a perl script.
>
>Fascinating. Is it in the CVS? It's not jumping out at me.

It's part of the sources.redhat.com infrastructure.  It is in CVS but it
is not intended for general use.  I don't know if it is even available
for anonymous CVS access.

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

I'm not interested in supporting another package so your best option is
to write your own.

I am not really understanding your confusion, though.  Some of the
information is in setup.hints, some is in setup.ini.  setup.hint takes
precedence, of course.

Eventually all of the information will be in setup.hint but there is no
pressing need for this to be the case.

In case it isn't really clear, I'm not really interested in making
setup.exe a general purpose tool for you to use internally.  That has
never been a goal, and I see nothing but headaches from moving in that
direction.

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/