Re: getting new VMS extensions into Perl (was Re: [blead 2009-05-29.22:08:17] vms.c EFS logical name fix.)
Craig A. Berry wrote: On Jun 10, 2009, at 7:29 PM, John E. Malmberg wrote: Thomas Pfau wrote: John E. Malmberg wrote: We really need to get some sort of logical name support that we can count on being bundled with Perl on VMS. My VMS::Logical module appears to work. I don't think I ever uploaded it to CPAN but I could do that. http://axp1.nbpfaus.net/~pfau/perl/VMS-LOGICAL-0_3.ZIP That would be great. If that poses any problem for you I'd be happy to do it with your permission. No problem. I have a PAUSE account. I'll try to remember to upload it tonight. -- tom_p http://nbpfaus.net/
Re: getting new VMS extensions into Perl (was Re: [blead 2009-05-29.22:08:17] vms.c EFS logical name fix.)
On Jun 10, 2009, at 10:09 PM, John E. Malmberg wrote: Craig A. Berry wrote: Get them on CPAN and other possibilities arise, though probably not before Perl 5.12.0. If we can get them into CPAN, would it be acceptable to make them a requirement for other CPAN modules to use them just on the VMS platform? No, I don't think you can require anybody else to use your module in theirs. You can of course suggest it. The point of getting something onto CPAN is that it provides a baseline of open source credibility. People can see what's there, file bug reports against it, report test results, etc. Plus I think the main value of having VMS::Logical and VMS::Feature on CPAN is that people can find and use them because they'll be in the most common place to look for such things. I'm not entirely convinced we need them in the core. What we mainly need for the core is a way to distinguish concealed device names from similar-looking logical names. We may be able to do that with tweaks to VMS::Filespec::rmsexpand or something in the neighborhooed. Craig A. Berry mailto:craigbe...@mac.com ... getting out of a sonnet is much more difficult than getting in. Brad Leithauser
Re: getting new VMS extensions into Perl (was Re: [blead 2009-05-29.22:08:17] vms.c EFS logical name fix.)
On Jun 11, 2009, at 7:59 AM, Thomas Pfau wrote: Craig A. Berry wrote: On Jun 10, 2009, at 7:29 PM, John E. Malmberg wrote: Thomas Pfau wrote: John E. Malmberg wrote: My VMS::Logical module appears to work. I don't think I ever uploaded it to CPAN but I could do that. http://axp1.nbpfaus.net/~pfau/perl/VMS-LOGICAL-0_3.ZIP I have a PAUSE account. I'll try to remember to upload it tonight. Note that PAUSE now rejects any archive containing any file or directory that is world writable and I think the MakeMaker distribution targets create directories that way by default. In any case I remember having to manually turn off world access to everything before zipping it up the last time I uploaded anything. Craig A. Berry mailto:craigbe...@mac.com ... getting out of a sonnet is much more difficult than getting in. Brad Leithauser
getting new VMS extensions into Perl (was Re: [blead 2009-05-29.22:08:17] vms.c EFS logical name fix.)
On Jun 10, 2009, at 7:29 PM, John E. Malmberg wrote: Thomas Pfau wrote: John E. Malmberg wrote: We really need to get some sort of logical name support that we can count on being bundled with Perl on VMS. My VMS::Logical module appears to work. I don't think I ever uploaded it to CPAN but I could do that. http://axp1.nbpfaus.net/~pfau/perl/VMS-LOGICAL-0_3.ZIP That would be great. If that poses any problem for you I'd be happy to do it with your permission. That is a start, but we need it as part of the base Perl distribution on VMS. There is considerable interest currently in removing extensions from the core and reluctance to add them. This derives from somewhat of a binge in adding new extensions in recent years that add to the maintenance burden of the core developers at a time when the core developers have become spread rather thin. The basic criteria now are that to be in core an extension should be essential for building Perl and/or installing other extensions. Arguably VMS::Feature and VMS::Logical could meet these criteria since they expose aspects of the environment that are of interest when building things. But as far as anyone who would have any say in incorporating them is concerned, they don't exist because they are not on CPAN. Get them on CPAN and other possibilities arise, though probably not before Perl 5.12.0. Craig A. Berry mailto:craigbe...@mac.com ... getting out of a sonnet is much more difficult than getting in. Brad Leithauser
Re: getting new VMS extensions into Perl (was Re: [blead 2009-05-29.22:08:17] vms.c EFS logical name fix.)
Craig A. Berry wrote: On Jun 10, 2009, at 7:29 PM, John E. Malmberg wrote: There is considerable interest currently in removing extensions from the core and reluctance to add them. This derives from somewhat of a binge in adding new extensions in recent years that add to the maintenance burden of the core developers at a time when the core developers have become spread rather thin. The basic criteria now are that to be in core an extension should be essential for building Perl and/or installing other extensions. Arguably VMS::Feature and VMS::Logical could meet these criteria since they expose aspects of the environment that are of interest when building things. But as far as anyone who would have any say in incorporating them is concerned, they don't exist because they are not on CPAN. Get them on CPAN and other possibilities arise, though probably not before Perl 5.12.0. If we can get them into CPAN, would it be acceptable to make them a requirement for other CPAN modules to use them just on the VMS platform? Regards, -John wb8...@qsl.net Personal Opinion Only
