Michael G Schwern <[EMAIL PROTECTED]> wrote on 03/13/2005 06:34:27 PM:

> As mentioned here, I want to break up MakeMaker.
> http://www.makemaker.org/wiki/index.cgi?ModulesForSale
> 
> There's a number of modules which are just utilities MakeMaker uses and 
I
> want them out in their own distribution.  But I have to be careful not 
to 
> introduce a circular dependency.  So ideally MakeMaker would continue to
> come bundled with its own copies of those modules.  This looks like a
> job for Module::Install!  The question is, how portable is it?  And 
what's
> the minimum version of Perl it will run on?
> 

I didn't have any luck with Module::Install under OpenVMS/AXP 7.1-1. It 
does a fair amount of direct manipulation of @INC in ordinary 
circumstances, and even more on the install, because it tries to bootstrap 
itself from its own blib directory.

Specifically, it makes the assumption that it can push (e.g.) 'blib' on 
the stack and have it be interpreted as that 'blib' which is a 
subdirectory of the current directory. This doesn't work under VMS, where 
what you want is '[.blib]'.

I tried some desultory conditionalizing on $^O, but never really got 
anywhere. The real problem may have been that, as badly as I personally 
wanted to install Net::LDAP and reset peoples' Windows passwords under 
VMS, I couldn't justify to myself spending my employers' time on it.

My bottom line is that Module::Install requires filename semantics not too 
far from those of Unix, and while (e.g.) Windows is close enough, VMS 
isn't by a long shot.

Tom Wyant


This communication is for use by the intended recipient and contains 
information that may be privileged, confidential or copyrighted under
applicable law.  If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited.  Please notify the sender
by return e-mail and delete this e-mail from your system.  Unless
explicitly and conspicuously designated as "E-Contract Intended",
this e-mail does not constitute a contract offer, a contract amendment,
or an acceptance of a contract offer.  This e-mail does not constitute
a consent to the use of sender's contact information for direct marketing
purposes or for transfers of data to third parties.

 Francais Deutsch Italiano  Espanol  Portugues  Japanese  Chinese  Korean

            http://www.DuPont.com/corp/email_disclaimer.html


Reply via email to