Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
I'm using a GUI (unigetui) as a frontend to winget-cli, and would like to save a batch of --location overrides it its app profiles. But I'd like those profiles to be portable across machines, so would like to be able to use environment variables in paths that would resolve to differnt paths on different machines
For that it would help if winget supported environment variable expansion in its interface that doesn't depend on external tools (shells/apps)
Proposed technical implementation details
Since / : * ? " < > | are illegal in folder names, maybe you could use <> to denote env vars?
--location "<SystemDrive>Program Files\my-app" would expand to C:\
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
I'm using a GUI (unigetui) as a frontend to winget-cli, and would like to save a batch of
--locationoverrides it its app profiles. But I'd like those profiles to be portable across machines, so would like to be able to use environment variables in paths that would resolve to differnt paths on different machinesFor that it would help if winget supported environment variable expansion in its interface that doesn't depend on external tools (shells/apps)
Proposed technical implementation details
Since
/ : * ? " < > |are illegal in folder names, maybe you could use<>to denote env vars?--location "<SystemDrive>Program Files\my-app"would expand toC:\