Ash258 / Scoop-Core

Shovel. Alternative, more advanced, and user-friendly implementation of windows command-line installer scoop.

Home Page:https://shovel.ash258.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

installing to custom path requires the SCOOP environment variable to be set

bitoolean opened this issue · comments

  • Branch: Main
  • Powershell Version: 7.2

I was following the installation instructions.
I decided to install Scoop to a custom path.
Got an error at the "scoop update" step in the Shovel installation instructions (the error ocurred at line 52 in Update.ps1, on "Remove-Item $TargetDirectory" and on the next line "Move-Item $newDir $TargetDirectory" that it couldn't find the path it was looking for under the user profile directory (of course - that's the default location and I installed Scoop in a different path).

Workaround:
The status or the checkup command told me, among other things, it's recommended to have the SCOOP environment variable set, so I did that and then opened a new powershell window (so it runs in a new process and sees the environment variable). Then the update command worked with no issues. I did have to run several commands as suggested by the checkup command at the end.

Suggestion: add this optional step to the Shovel install instructions for others who decide to install to custom path (if a fix is not preferred)?

Question: the status or the checkup command said the environment variable is recommended because there are probably packages out there still referencing it - should I keep it then? Update: I've answered my own question - it's needed as long as Shovel is still installed in the custom directory (not even search works).

OS: Windows 11