>> > It was the perl module stuff. I can't for the *life* of me get
>> > an answer about what to do about this from the namespace czars.
>I'll run the issue by other czars.
The issues are several.
What is the namespace to use for pod related utilities and
libraries? Should it be som
I suppose one could do something like this:
% perl -e 'system {"perlsub"} qw/perlman -l/'
/usr/local/man/man1/perlsub.1
/usr/local/lib/perl5/5.6.0/pod/perlsub.pod
/home/tchrist/perldoc/bin/perlsub
--tom
>That was why I mentioned a $(LNS) Makefile macro. On unix it's
>LNS= ln -s
>and on VMS it's
>LNS= copy
>I think on NT it is either 'copy' or 'xcopy'
Oh goodness, no! That defeats the whole purpose. First, you have
update issues between binary and module. Secondly
% ls /usr/local
> > It was the perl module stuff. I can't for the *life* of me get
> > an answer about what to do about this from the namespace czars.
I'll run the issue by other czars.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dea
On Fri, Sep 08, 2000 at 04:46:47PM -0700, Peter Prymmer wrote:
>
>
> On Fri, 8 Sep 2000, Tom Christiansen wrote:
>
> > But what about linking? tcgrep.pm should be the same file
> > as tcgrep the program. Every one of those .pm files is
> > both a module and a program.
>
> That was why I ment
On Fri, 8 Sep 2000, Tom Christiansen wrote:
> But what about linking? tcgrep.pm should be the same file
> as tcgrep the program. Every one of those .pm files is
> both a module and a program.
That was why I mentioned a $(LNS) Makefile macro. On unix it's
LNS= ln -s
and on VMS it's
LNS= c
On Fri, 8 Sep 2000, Tom Christiansen wrote:
> >And now I have tested some of the functionality. perlman.pm apparently
> >puts too much faith in the setting of $Config{pager} since on VMS we
> >leave that to 'most' which was not installed on my machine I had to
> >edit the two copies of Config.
>> OK, I have not yet tested any of the functionality but the first
>> obvious thing is that the tar ball itself is chock full of sym links
>> which are basically unix only (there are analogs on Win NT and Mac OS,
>And now I have tested some of the functionality. perlman.pm apparently
>puts too
On Fri, 8 Sep 2000, Peter Prymmer wrote:
> OK, I have not yet tested any of the functionality but the first
> obvious thing is that the tar ball itself is chock full of sym links
> which are basically unix only (there are analogs on Win NT and Mac OS,
And now I have tested some of the function
In case I wasn't clear, the state of affairs with the tarball
was simply a snapshot of what my current world looked like.
I was simply hoping the programs *ran*. I realize installation
is a different thing.
--tom
>OK, I have not yet tested any of the functionality but the first
>obvious thing is that the tar ball itself is chock full of sym links
>which are basically unix only (there are analogs on Win NT and Mac OS,
>and logical names serve the purpose on VMS but the former do not
>unpack with NT or Mac p
On Fri, 8 Sep 2000, Craig A. Berry wrote:
> Mike,
>
> I've once again forwarded your message to the list; I'm not
> especially fluent with the CGI.pm module and I think it was someone
> else who asked for the version you were using.
>
> >From: "Flaherty, Mike" <[EMAIL PROTECTED]>
> >To: "'[
Mike,
I've once again forwarded your message to the list; I'm not
especially fluent with the CGI.pm module and I think it was someone
else who asked for the version you were using.
>From: "Flaherty, Mike" <[EMAIL PROTECTED]>
>To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>Subject: Perl problem
On Fri, 8 Sep 2000, Tom Christiansen wrote:
> I don't know what you guys use for reading the perldocs, but
B is the default on VMS and is installed as a global
symbol (think alias in {t}csh) via the PERL_SETUP.COM DCL script
that is built as part of the Perl build on VMS.
> there's a snapsho
The following patch allows the build on VAX VMS V6.2 with DEC C 5.3:
diff -ru perl-5.7.0.orig/configure.com perl-5.7.0/configure.com
--- perl-5.7.0.orig/configure.com Fri Sep 1 10:08:25 2000
+++ perl-5.7.0/configure.comFri Sep 8 13:26:43 2000
@@ -4747,7 +4747,7 @@
$ WC "d_inetaton='
Peter Prymmer <[EMAIL PROTECTED]> writes:
> Well that is a relief. As to your question about whether this was the
> "best" place to discuss crinoid I do not know. But I certainly think
> that this is a very good and appropriate place to discuss it and I
> suspect that it may in fact be the best
A CC: to [EMAIL PROTECTED] wouldn't be a bad idea.
There _might_ be someone using crinoid on that list who doesn't also read this
list.
Although, really, I kind of doubt it...
> -Original Message-
> From: Peter Prymmer [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 08, 2000 3:00 P
On Fri, 8 Sep 2000, Tom Pfau wrote:
> My 'RMS$_DNR' problems were caused by cockpit error. I had copied the
> crinoid files from my test system to the live system forgetting that I had
> redirected a couple of logicals in TENTACLE.COM. Removing the offending
> lines allows the site to work cor
My 'RMS$_DNR' problems were caused by cockpit error. I had copied the
crinoid files from my test system to the live system forgetting that I had
redirected a couple of logicals in TENTACLE.COM. Removing the offending
lines allows the site to work correctly.
Thomas Pfau
[EMAIL PROTECTED]
aka [EMA
On Fri, 8 Sep 2000, Peter Prymmer wrote:
> diff -ru perl-5.7.0.orig/Makefile.SH perl-5.7.0/Makefile.SH
> --- perl-5.7.0.orig/Makefile.SH Mon Aug 28 18:05:57 2000
> +++ perl-5.7.0/Makefile.SHFri Sep 8 09:40:11 2000
> @@ -730,7 +730,7 @@
I neglected to mention that this worked just fi
Hi,
I would like to add t/ran_tests handling to the VMS Makefile, but when I
looked at the current implementation I realized that at 9 characters the
generated file is just over the 8.3 limitation of DOS/FAT16. Hence I
propose the following modification to the only two files that currently
menti
I'm attempting to run our site under crinoid. It works fine if run directly
from the web server using a 'map' directive. When I change this to an
'exec' to run under crinoid, attempts to access the data files with
VMS::IndexedFile fail with '%RMS-E-DNR, device not ready, not mounted, or
unavaila
Larry Bohan has pointed out that using VMS::Stdio's vmsopen
works correctly on 7.2-1. This doesn't explain why Perl's
vanilla open doesn't work on 7.2-1 when it did on 7.1, but
at least now there's a workaround. Whoever's got the VMSperl
doc pumpkin smelling up their office might want to include
"Craig A. Berry" wrote:
[...]
> This will probably do it. I don't have DECNET set up on my 7.2-1
> machine (or any other nodes to talk to), so I don't know what it does
> remotely. If this works on 7.1 but not 7.2-1, then the C RTL has
> probably been "improved" in ways that break what you are d
Some more details on the "extra LF's issue"...
What we have is the following heirarchy of processes:
MMS/K
[.vms]test.com
perl (running some test)
In the old (pre-piping mod) scheme of things, the SYS$ERROR output of
a subprocess would willy-nilly be combined with i
I don't know what you guys use for reading the perldocs, but
there's a snapshot of a new version out there in
http://doriath.perl.com/misc/perlman-alpha0.tar.gz
There are announcements on comp.lang.perl.misc and p5p about it
for more details.
I've only tested it on a couple different syste
> -Original Message-
> From: Peter Prymmer [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 07, 2000 5:58 PM
> To: Jordan Henderson
> Cc: 'John Peacock'; Craig A. Berry; '[EMAIL PROTECTED]'
> Subject: RE: extra LFs in test output (was Re: current status of
> 6919with3 patches on DE
I saw this same behavior, but I attributed it to having an incompatible
PERL_ROOT
logical defined when I was trying to do the build.
I've not seen it since, but it may have been a coincidence that it stopped
happening
after I cleaned up my environment.
> -Original Message-
> From: Craig
28 matches
Mail list logo
