What part of Perl doesn't like NTFS Junctions?

I like the Vista style for the path, so on XP I created NTFS transitions C:\Users β†’ C:\Documents and Settings and ~\Documents β†’ ~\My Documents , so I only had to write one style of the path C:\Users\me\Documents .

However, CPAN::SQLite and Exporter are hairy when I set PERL5LIB to 'C:\Users\me\Documents\dev\perl\lib' . Exporter modules that inherit from Exporter complain that export_to_level not detected when they try to use it.

I really think this is Exporter et al., And CPAN::SQLite is just a victim because it imports the $dbh character in the usage statement, only to let perl complain that $dbh is undefined. Additionally, XS-related modules complain about the lack of a β€œbootstrap” method.

Does anyone know if Perl (Strawberry) has a specific problem with NTFS connections?

+6
source share
1 answer

This is not so much the answer to the question: I could not recreate the problem. Therefore, I can not reliably reproduce the error message. It was not just a reboot. Because I made a few of them.

I changed my PERL5LIB to " C:\Documents and Settings\me\My Documents\... ", running some Perl, and just decided that it should be so.

Then I read the ikegami question in the comments and changed the Windows setting to C:\Users\me\Documents\...\perl\lib , and Perl still worked fine - it was also CPAN. I rebooted, making sure that the environment variable is set by the Junction names, and still perl and CPAN are working fine.

For the few weeks since I posted this question, I have never seen a problem again. And now here is the perl environment in which I run:

 C:\blahblahblah>perl -MSmart::Comments -MCPAN::SQLite -e "### @INC" ### @INC: [ ### 'c:/Users/<me>/Documents/.../perl/lib', ### 'C:/strawberry/perl/site/lib', ### 'C:/strawberry/perl/vendor/lib', ### 'C:/strawberry/perl/lib', ### '.' ### ] 

The thing is, when I started the "old path", I could reorganize my personal perl / lib to fix another problem.

But I think the answer is that Strawberry Perl probably has no problems with NTFS Junctions ... in the end.

+1
source

Source: https://habr.com/ru/post/886333/


All Articles