Details
Description
Splitting PUP-4866 for PMT and Plug-in Sync to have a ticket for each effort.
This is the PMT effort
It was discovered in PUP-4854 that long file name paths will break PMT and potentially plugin-sync. The PMT and Puppet core libraries should always use LFN (Long File Name aka "\\?\") paths for module installation to avoid long file name issues.
In PUP-4854 we reduced the amount of characters that PMT uses so that it allows for longer module paths to be installed. It helps with longer paths in modules, but it doesn't address the issue completely. We should instead look to use "\\?\" prepended to the path to allow for up to 32,000 characters in paths instead of the current MAX_PATH limit of 260 characters. See MSDN - Naming Files, Paths, and Namespaces.
Attachments
Issue Links
- blocks
-
MODULES-2668 DSC - Plug-in Sync Fails on Windows 2003 R2
-
- Resolved
-
- clones
-
PUP-4866 Plugin Sync Should Use Long File Name (LFN) Paths on Windows
-
- Closed
-
- is blocked by
-
MODULES-4929 Spike - PUP-4866 (LFN Paths on Windows) and PUP-6152 Research solution approach
-
- Closed
-
- relates to
-
PUP-8257 Puppet::FileSystem::Windows should support LFN
-
- Closed
-
-
MODULES-2408 DSC - Document PMT long file name issue
-
- Resolved
-
-
PUP-4866 Plugin Sync Should Use Long File Name (LFN) Paths on Windows
-
- Closed
-
-
PUP-4854 PMT fails to install modules on Windows that have long paths
-
- Closed
-
-
PUP-4866 Plugin Sync Should Use Long File Name (LFN) Paths on Windows
-
- Closed
-