X-Spam-Check-By: sourceware.org
Message-ID: <b22700f10701291019r30a2ecg9b423e50d88ec433@mail.gmail.com>
Date: Mon, 29 Jan 2007 10:19:02 -0800
From: "Mark Wendell" <mark DOT wendell AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: plans for PIL installer?
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Just curious to know if anyone is planning on creating a python
imaging library install for cygwin setup...

I found an old thread where someone discusses the steps he went
through to do this a while ago (
http://www.cygwin.com/ml/cygwin/2003-06/msg01121.html ), but it seems
like these are some pretty involved and error-prone procedures for
casual users to follow.

thanks
Mark


-- 
--
Mark Wendell
mark DOT wendell AT gmail DOT com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/