Replies: 2 comments 1 reply
-
@AFulgens I was just about to add it to the documentation when I put on my glasses. It's there: |
Beta Was this translation helpful? Give feedback.
-
It is there that it must be an absolute path. If I have an envrionment variable via
then My problem is that To quote from my original post:
|
Beta Was this translation helpful? Give feedback.
-
https://github.com/microsoft/winget-cli/blob/master/doc/Settings.md tells me that I can define installations paths for (non-)portable installations with
The documentation also tells me that these must be absolute paths (totally legitimate restriction), with defaulting to
%LOCALAPPDATA%/Microsoft/WinGet/Packages/
and%PROGRAMFILES%/WinGet/Packages/
respectively, in case they are not defined.Thus, I conclude that I can use CMD-style variables in the paths, i.e., I would expect
%USERPROFILE%/.winget/
to work.Alas, it results in a validation failure:
Either the documentation should say that it must be an absolute path and no variables are allowed, or winget should dereference variables.
Am I missing something here?
Beta Was this translation helpful? Give feedback.
All reactions