I have a problem using Archive::Zip on Windows Server 2003.
The problem is that when doing an "addTree" Archive::Zip walks the tree using File::Find which in my case dies in a particular directory because it fails to do chdir ../../../../../../../../../../../..
The interesting thing now is that when I open a cmd.exe-shell and navigate to this directory and try to do a "cd ../../<and so on>" it also fails, so it seems to me I am running into a Windows-specific limitation.
The path-length of the directory where this problem occurs is 225 characters and the length of the ../..-part is 35 characters, so together it is 260...
I have made some experiments and it seems to me that on Windows if you are in a directory and you try to do a "cd <upwards-only>" then that fails if the pathlength of the directory plus the path-length of the upward-path exceeds 260 (or so).
Is that really true?
If that is the case, how would you work around it when using Archive::Zip or File::Find?
Many thanks!
In reply to File::Find problem on Windows by morgon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |