Open
Description
Hello,
As we are trying to update our Rez version from 2.91, I noted that the resolution now uses UNC paths:
Rez v2.112.0
C:\Users\tmansencal>rez-env dcraw
You are now in a rez-configured environment.
resolved by tmansencal@***, on Fri Feb 03 08:48:25 2023, using Rez v2.112.0
requested packages:
dcraw
~platform==windows (implicit)
~arch==AMD64 (implicit)
~os==windows-10.0.***.SP0 (implicit)
resolved packages:
arch-AMD64 c:\***\packages\***\arch\AMD64
dcraw-9.27 \\***\***\packages\thirdparty\dcraw\9.27\platform-windows\arch-AMD64
platform-windows c:\***\packages\***\platform\windows
Rez v2.2.91.0
C:\Users\tmansencal>rez-env dcraw
You are now in a rez-configured environment.
resolved by tmansencal@***, on Fri Feb 03 08:53:09 2023, using Rez v2.91.0
requested packages:
dcraw
~platform==windows (implicit)
~arch==AMD64 (implicit)
~os==windows-10.0.***.SP0 (implicit)
resolved packages:
arch-AMD64 c:\***\packages\***\arch\AMD64
dcraw-9.27 s:\packages\thirdparty\dcraw\9.27\platform-windows\arch-AMD64
platform-windows c:\***\packages\***\platform\windows
Environment
- OS: Window 10
- Rez version (eg "2.100.0"): v2.112.0
- Rez python version (output of "rez-python --version"): Python 3.10.9
I do think that this is strictly caused by the Python difference but would be keen to know if anyone has seen that already before I start digging.
To Reproduce
- Build Rez with Python 3.7, resolve environment from mounted drive.
- Build Rez with Python 3.10, resolve environment from mounted drive.
- Compare the resolved package paths.
Expected behavior
The mounted drive package path should be used as UNC paths wreck havoc in many CMD scripts.
Actual behavior
The UNC package path is used instead.