Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Sun, 29 Aug 2004 13:52:52 +0200
From: "Gerrit P. Haase" <gp@familiehaase.de>
Reply-To: "Gerrit @ cygwin" <cygwin@cygwin.com>
Organization: Esse keine toten Tiere
Message-ID: <919640362.20040829135252@familiehaase.de>
To: cygwin@cygwin.com
Subject: Re: understanding effects of moving addons from site_perl to vendor_perl
In-Reply-To: <008501c48db8$4b9e7030$78d96f83@robinson.cam.ac.uk>
References: <413144A1.3060900@tlinx.org> <008501c48db8$4b9e7030$78d96f83@robinson.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Hello Max,

> It's essentially a lack of planning/coordination between the perl and
> perl-libwin32 maintainers.

The libwin32 maintainer is not following the list and discussion.
I think I can include libwin32 with the main perl package, but there
are problems building it, there is a bug in some w32api headers and
one part is not building at all (OLE).


GErrit
-- 
=^..^=



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