Can we change the version logic when running
scoop update <manifest> to always install the bucket version even if it evaluates to a "lower" version then what is currently installed?
checkveris for checking for program updates and downloading/calculating the checksum. It updates the
*.jsonfile and you can create a pull-request. (all apps in official bucket get updated automatically by https://github.com/ScoopInstaller/Excavator)
checkverinformation of the json file) then it will get updated. The logfiles can be found here: https://scoop.r15.ch/
Hi Scoop community!
I've run through the issue section and wiki on GitHub in search for this, but have come up empty. I really enjoy how Scoop isolates installs to a single directory and isn't relying or requiring admin privileges, but I was wondering whether it's possible to change the installation path?
$ scoop install python # ends up in %userprofile%\scoop $ scoop install python --prefix c:\my\custom\dir # ends up in c:\my\custom\dir
Some approaches I've considered are:
%userprofile%\scoopto "trick" scoop into installing elsewhere.
But was hoping for something simpler. Alternative one doesn't work, for example, if the user already has apps installed there, unless I delete those first.
SCOOP_HOMEenvironment variables used by AppVeyor, and they seem to do the trick, somewhat. They don't appear editable post-install, as Scoop complains about directories missing, and about Scoop itself not being available in
apps/which is understandable. For now, since I'm calling this from within a script/wrapper, I'm working around it by recreating the SCOOP_HOME directory structure, including
apps/scoopprior to installing any apps. Not ideal, and am still interested to hear of alternatives!
SCOOP_HOMEis only used by the bucket scripts in
auto-pr.ps1, See: https://github.com/ScoopInstaller/Main/tree/master/bin)