scoop install
letting people view the JSON file before deciding if they want to proceed with the installation? That might be a simple way to give end users more power to see what they install.
scoop virustotal <app>
is a good enough way to inspect and analyze suspicious files of a package, I think.
May be of interest to some here:
I don't always have access to PowerShell & Git to update my own external bucket, so using a modified appveyor.yml
+ checkver.ps1
I now automatically update any app manifests when the AppVeyor CI build runs:
https://gitlab.com/xeijin-dev/propositum-bucket/blob/master/appveyor.yml
@xeijin, you probably copied the junction folders (e.g. 'current' and persisted directories) as folders. XCOPY does that. It's said that FastCopy does the trick (haven't tried it)
By the way @niboan thanks for your help. I did eventually find the issue (though would have found it even quicker had I read your mention!)
I was 7zip-ing the entire contents of the scoop folder for upload to BinTray as an artifact. However the .7z
format doesn't support junctions/symlinks.
To workaround this I first had to create a .tar
archive with 7zip (which preserves the symlinks) and then create a .7z
archive from the .tar
to get the filesize down, as .tar
doesn't support compression.
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?
Reasons:
checkver
is for checking for program updates and downloading/calculating the checksum. It updates the *.json
file and you can create a pull-request. (all apps in official bucket get updated automatically by https://github.com/ScoopInstaller/Excavator)
checkver
information of the json file) then it will get updated. The logfiles can be found here: https://scoop.r15.ch/