Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Mon, 30 Aug 2004 07:18:54 +0200
From: "Gerrit P. Haase" <gp AT familiehaase DOT de>
Reply-To: "Gerrit @ cygwin" <cygwin AT cygwin DOT com>
Organization: Esse keine toten Tiere
Message-ID: <1748313440.20040830071854@familiehaase.de>
To: linda w <cygwin AT tlinx DOT org>
CC: "Gerrit @ cygwin" <cygwin AT cygwin DOT com>
Subject: Re: understanding effects of moving addons from site_perl to vendor_perl
In-Reply-To: <4132716E.1010502@tlinx.org>
References: <413144A1 DOT 3060900 AT tlinx DOT org> <008501c48db8$4b9e7030$78d96f83 AT robinson DOT cam DOT ac DOT uk> <919640362 DOT 20040829135252 AT familiehaase DOT de> <4132716E DOT 1010502 AT tlinx DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Hello linda,

Am Montag, 30. August 2004 um 02:14 schriebst du:


>> 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).

> That would be cool if there was 1 package -- would more guarantee
> them being in sync.  I tend to agree...I guess I was lucky before
> this -- either I got the libwin32 with the perl-dist, or libwin32
> has been kept in sync with perl.  Maybe the next release of perl was
> kept in the "Experimental"  state until the lib was sync'ed?

Well, you may keep the previous until libwin32 is updated.

> Why would there be a bug in building it?  Has the win32 interface
> changed since the last perl release or did the cygwin headers
> somehow get mangled? Strange.

There is one problem with changed gcc behaviour, a switch is needed
--enable-stdcall-fixup probably, then there is another unresolved
problem with the OLE module.


> I wasn't aware that all modules have to be re-installed with
> each bug-fix release as Reini suggests. I would have guessed that
> it should only be necessary (and maybe not even then) between
> major (5.4->5.6, 5.6->5.8, etc.) releases.  Oh well.

I'm thinking about changing the naming scheme, to reflect this.


> I think it'd be great if the win32-lib library became part of the
> perl-win32 release.  It seems that which perl is often used for
> (system admin scripts and such) would be more difficult or not
> possible without the win32 interface.
> It would also make for a more stable win32 development platform, I
> think. 

> Occasionally, I send emails to the "scripting guys" at Microsoft
> asking to show some of their scripting talents in something other
> than Visual Basic or some proprietary MS language.  Would be sorta
> neat if they demo'ed using standard scripting languages such as
> bash, perl or python to do system management/ maintenance tasks.  I
> refer them to the cygwin platform as being a good place to
> experiment with such languages and I've heard that perl is used
> internally by programmers (not sure for what, though)...

Windows comes with perl (well as an addon in the resource kit) since
nearly 10 years.

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/