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
Reply-To: <nhv AT cape DOT com>
From: "Norman Vine" <nhv AT cape DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: building cygwin with python script
Date: Wed, 27 Jun 2001 21:29:36 -0400
Message-ID: <00d201c0ff71$cb37e840$a300a8c0@nhv>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To: <20010627203942.A26445@redhat.com>
Importance: Normal

Christopher Faylor writes:
>
>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".

I will try to keep the python script at its current location but
in general anything on my website is only transitory at best.

I am delighted if it helps anybody.

However it is very long winded and IMHO not the best
example of how this could be done or of Python use for 
that matter. 

I really have little interest in 'officially' maintaining it and
if it is used IMO should definitely have "use at yout own risk" 
stamped all over it.

If someone else wants to give the script a home and maintain it,  
please feel free to do so,  but as I said in my original post 
"I am sure there are better ways to do this"

FWIW
I originally wrote this just as an exercise in seeing how
to go about doing this kind of thing not ever intending
for it to be 'exposed' to public scrutiny but then when it 
seemed as if I might be able to help put and end to a VERY
LONG thread by proffering a 'cookbook' method to building
the cygwin dll  .............

Cheers

Norman


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