X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.1 required=5.0	tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <1282535618.6888.51.camel@YAAKOV04>
References: <1282535618 DOT 6888 DOT 51 DOT camel AT YAAKOV04>
Date: Mon, 23 Aug 2010 15:36:22 +0200
Message-ID: <AANLkTimGT6cp8z-dAS=YHZM4fcOwi-Fn4xZtDL=tKhWS@mail.gmail.com>
Subject: Re: perl: Net::DNS requires Win32::IPHelper
From: Reini Urban <rurban AT x-ray DOT at>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

2010/8/23 Yaakov (Cygwin/X) <yselkowitz AT users DOT sourceforge DOT net>:
> Reini,
>
> The Net::DNS module, which you ship with perl, depends on perl-libwin32
> (packaged separately) and Win32::IPHelper, the latter of which depends
> on Win32::API and enum modules. =A0Win32::API needs a custom typemap file
> in order to compile on Cygwin, which AFAICS should be:
>
> TYPEMAP
> HINSTANCE =A0 T_PTR
> LPCSTR =A0 =A0 =A0T_PV
> LPCWSTR =A0 =A0 T_PV

Oh my. Net::DNS depending on Win32::API is not really helpful.
He already has a DNS.xs it would be easy to add the IPHelper stuff to this =
xs.
perl-libwin32 is a bit fat for a perl require line, I'll see what I
can do to remove this cyclic dependency.
Net::DNS is only needed for the old CPAN::Reporter.
The new CPAN::Reporter 2.0 will use Metabase and has a entirely
different set of deps.

I have somewhere a proper Win32::API cygwin package but never wanted to
support that mess. http://rurban.xarch.at/cygc/perl-Win32-API/

> Again, I'm going to have to ask you to break out the extra modules you
> ship with perl and handle them individually. =A0It's not only a matter of
> handling these dependencies, but there are several modules which need to
> be updated, and you shouldn't have to rebuild (nor should we have to ask
> you to rebuild) all of perl in order to do so.

Ok, I will provide the extra vendor modules as perl-modules or perl-extra p=
kg.
But this will happen with 5.14, which is the next planned cygwin
release in spring 2011.

All vendor modules together or split it into the dependencies?
perl-CPAN needs
        Pod::Escapes Pod::Simple Test::Pod Devel::Symdump
Pod::Coverage Test::Pod::Coverage \
	Compress::Raw::Bzip2 IO::Compress::Bzip2 Compress::Bzip2 \
        IO::String \
        File::Temp Archive::Zip \
	Math::BigInt::FastCalc \
	Term::ReadKey Term::ReadLine::Perl Term::ReadLine::Gnu \
        XML::NamespaceSupport XML::SAX XML::LibXML::Common XML::LibXML \
	XML::Parser \
	Proc::ProcessTable \
	YAML \
	Config::Tiny File::Copy::Recursive IPC::Run3 Probe::Perl  \
    	Tee IO::CaptureOutput File::pushd File::HomeDir \
	Digest::SHA \
	Module::Signature \
        URI HTML::Tagset HTML::Parser LWP
        CPAN

perl-CPAN-Reporter needed:
   Net::DNS Test::Reporter CPAN::Reporter
but now with Metabase it's much fatter. About 15-20 modules or so,
where some do not work out
of the box.
I really want to support sending cpan reports out of the box, because
most developers are happy
to get failing cygwin reports. (linker strictness and IV vs pointer size mo=
stly)

Note this is not really an issue for most users, because I explicitly
changed the @INC order
so that you can override the vendor modules with cpan installed site module=
s.
But for your port modules it is an issue of course.
--=20
Reini Urban

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