Peter Prymmer <[EMAIL PROTECTED]> wrote:
|
| Charles Bailey wrote:
|
| > > What do folks here think of an addition to perlrun.pod such as this?:
| >
| > Looks like a good idea. Would it fit better into perlvms.pod?
|
| Thanks. The wording was intended to fit in with the wording of
| perlrun.
Charles Lane <[EMAIL PROTECTED]> wrote:
|
| How about this as an alternative for finding VMSPIPE.COM:
|
| translate logical PERL_VMSPIPE_DURING_MAKE in LNM$PROCESS,
| and if present, use it.
| else look for a readable PERL_ROOT:[00]VMSPIPE.COM, if found use it.
| ...oth
> At 10:29 AM 4/3/00 -0700, [EMAIL PROTECTED] wrote:
> >Dan Sugalski wrote:
>> > couldn't succeed if that weren't the case)
> >
> >I think a hardcoded PERL_ROOT:[LIB] or an @INC lookup (though I'm not
> >sure about @INC since miniperl does use it) runs into trouble with the
> >"need" to have PERL_
Chuck Lane wrote:
> Well, as far as I can tell the *only* place having VMSPIPE.COM in
> PERL_ROOT:[00] could *maybe* be an issue is during the Perl
> build/test/install.
>
> But that all occurs in what (should be) a rather well controlled
> environment. As has been mentioned, MMK and MMS do
Charles Bailey wrote:
> > What do folks here think of an addition to perlrun.pod such as this?:
>
> Looks like a good idea. Would it fit better into perlvms.pod?
Thanks. The wording was intended to fit in with the wording of
perlrun.pod, in particular the (Win32 port only) type env. var. lis
Chuck Lane wrote:
> I don't think so; checking the DESCRIP.MMS:
>
> install : $(MINIPERL_EXE)
> @ @perl_setup.com
> If F$TrnLnm("Sys") .nes. "" Then Deass SYS
> $(MINIPERL) installperl
>
> So even if you play around with definitions of PERL_ROOT earlier, the
> execut
Craig A. Berry wrote:
> At 10:23 PM -0500 3/31/00, Charles Lane wrote:
> >
> >Avoiding dependance on having the logicals set up properly *before*
> >invoking "MMK test", sure... but MMK should be able to set up some
> >logicals that the build and test code depend on.
>
> Isn't the problem that i
Dan Sugalski <[EMAIL PROTECTED]> writes:
> At 11:17 AM 4/3/00 -0400, Charles Lane wrote:
>> > How 'bout doing a regular @INC lookup, and installing vmspipe.com in
>> > the library?
>>
>>Hmmmthat's got a ton of implications, you know.
>>
>>For example, a user's script mucks around with @INC and
At 11:17 AM 4/3/00 -0400, Charles Lane wrote:
>This should have been CC:'d to vmsperl
>
>- Start of forwarded message[s] -
>Return-path: <[EMAIL PROTECTED]>
>Date: Mon, 3 Apr 2000 11:15:47 EDT
>From: lane (Charles Lane) @ DUPHY4.Physics.Drexel.Edu
>Message-Id: <[EMAIL PROTECTED]>
>
This should have been CC:'d to vmsperl
- Start of forwarded message[s] -
Return-path: <[EMAIL PROTECTED]>
Date: Mon, 3 Apr 2000 11:15:47 EDT
From: lane (Charles Lane) @ DUPHY4.Physics.Drexel.Edu
Message-Id: <[EMAIL PROTECTED]>
Subject: Re: [ID 2330.044] Not OK: perl v5.6.0 on
At 10:50 AM 4/3/00 -0400, Charles Lane wrote:
>But there's something odd: only a few of the VMS:: modules are
>available via CPAN.pm, considerably fewer than are actually present on
>CPAN. Note that "not available via CPAN.pm" generally means that the
>modules in question, while archived on CPAN
"Craig A. Berry" <[EMAIL PROTECTED]> writes:
>
> Isn't the problem that if MMS TEST defines or redefines PERL_ROOT and
> you then proceed (as would ordinarily be the logical next step) to do
> an MMS INSTALL you will be installing the build tree on top of itself
> rather than in wherever PERL_ROOT
Charles Lane <[EMAIL PROTECTED]> wrote:
|
| A patch for the glob-basic test was posted here on 17 Mar.
It's in the repository, but I think it just missed being wrapped
into the 5.6.0 kit as sarathy was trying to minimize changes.
The GLOB_NOCASE question is stil up in the air (briefly: would
it
> What do folks here think of an addition to perlrun.pod such as this?:
Looks like a good idea. Would it fit better into perlvms.pod?
Regards,
Charles Bailey [EMAIL PROTECTED]
In the course of getting CPAN.pm working on VMS, some of the first
modules that I tried building have been the VMS:: modules with
fewer (zero!) embedded unixisms, installation should be smooth and
easy.
But there's something odd: only a few of the VMS:: modules are
available via CPAN.pm, co
How about using LIB$GET_FOREIGN ?
This returns the command line parameters without expanding file names. The
command line is converted to upper-case, unless protected by double-quotes.
[It is the CRTL which later converts it to lower-case.] The command name
itself is not included, so for example:
"Craig A. Berry" <[EMAIL PROTECTED]> writes:
> At 10:23 PM -0500 3/31/00, Charles Lane wrote:
>>
>>Avoiding dependance on having the logicals set up properly *before*
>>invoking "MMK test", sure... but MMK should be able to set up some
>>logicals that the build and test code depend on.
>
> Isn't
17 matches
Mail list logo
