X-Spam-Check-By:	sourceware.org
Message-ID:	<456CFE72.4000204@users.sourceforge.net>
Date:	Tue, 28 Nov 2006 21:28:50 -0600
From:	"Yaakov S (Cygwin Ports)" <yselkowitz AT users DOT sourceforge DOT net>
User-Agent:	Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: cygport bug
References:	<456AF27D DOT 1040208 AT byu DOT net> <456AF4D8 DOT 8000703 AT byu DOT net> <456BB0E6 DOT 8050200 AT users DOT sourceforge DOT net> <456C38D6 DOT 9070306 AT byu DOT net>
In-Reply-To:	<456C38D6.9070306@byu.net>
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Eric Blake wrote:
> Thanks.  That hack to the Makefile seems better to me than hacking
> cygport.  I'll have to report that upstream.

I doubt that upstream will take the INSTALLDIRS=vendor part of the patch
as is, since different distros surely have different ways of using
vendor_perl/site_perl.  The other part of the patch dealing with cygwin
capabilities (d_ino and company) should definitely get pushed upstream,
however.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFbP5xpiWmPGlmQSMRAoB3AKDmYzu/mViOvA+R30Cyo3uZ//jspQCeJzrG
y3f2/v5z9ft4eFYZRMRPKWM=
=3luQ
-----END PGP SIGNATURE-----

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

- Raw text -