Green, Paul wrote:
Here's a sticky issue that is biting me as I verify perl-33218 on
Stratus VOS. I can use some advice.
We have a few restrictions on file names on our operating system. One
restriction is that don't allow file names to start with a hyphen.
Thus, the file:
perl-33218/t/Module_Pluggable/lib/OddTest/Plugin/-Dodgy.pm
cannot be extracted from the archive.
The default behavior of most of the VMS ports of TAR is to convert
illegal characters to '_' as they extract them.
What currently causes portability problems on VMS is names with more
than one dot in them, or directories with a dot in them.
In Perl 5.10 there are files that have multiple dots in them, and there
are Perl modules that require the file system to support this and other
non-portable characters.
Naturally, Configure's check against the MANIFEST file then fails. I
don't see any existing way to defeat this check. I guess I could update
README.vos to tell people to edit the MANIFEST file, but I'm looking for
something more automatic.
VMS currently uses a manually maintained Configure.com which has code to
deal with this.
There is also VMS specific code in vms.c and scattered through out Perl
that does this conversion.
One of the issues that I plan to be working on is that this name
mangling has not been needed on the ODS-5 file system and so any routine
that is doing the name mangling must be made more intelligent.
<snip>
Suggestions? Got a better idea?
I think it may be time for some routines that can do C<native_2_unix>
and C<unix_2_native> name conversions, that on unixish systems does
nothing, but will do the right thing for what ever the host platform does.
-John
[EMAIL PROTECTED]
Personal Opinion Only
