Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 27 Jun 2001 20:39:42 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: building cygwin with python script
Message-ID: <20010627203942.A26445@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <00cb01c0ff50$e309a2e0$a300a8c0 AT nhv> <3B3A6563 DOT 3050504 AT dufair DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <3B3A6563.3050504@dufair.org>; from jase@dufair.org on Wed, Jun 27, 2001 at 05:59:47PM -0500

On Wed, Jun 27, 2001 at 05:59:47PM -0500, Jason Dufair wrote:
>This is brilliant.  Nice cookbook.  Worked out of the box.  Exactly
>what is needed, IMO.  The calculated timings at the end are schweet.
>I'd like to suggest to the FAQ maintainer that this replace the section
>in the FAQ on "How do I build on NT?".  FAQ maintainer?  If it's OK,
>I'll do the changes.  I'd need CVS access since I assume anoncvs can't
>commit changes.  Maybe we can put the Python script on the
>sources.redhat.com site somewhere?

Ok.  I don't mean to shoot you down but I think that the FAQ should
really concentrate on how things are done.  So, it should focus on the
steps involved in building cygwin.

I would rather that people were familiar with what they were doing
rather than blindly relying on a python script.

I guess it can't hurt to make the python script available but I want
to be 100% certain that someone is willing to maintain it because you
KNOW that we'll start getting bug reports and "would be nice" reports
for it.

So, I would prefer that the cygwin FAQ contain rebuild instructions with
maybe a link to the python script as a "use at your own risk".

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/