Replies: 1 comment
-
Tracked here: #3894 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
From what I can find, when installing a specific package version that is different from the current manifest version, scoop just tries to generate the manifest based on the auto-update configuration of the manifest
Scoop/libexec/scoop-download.ps1
Lines 62 to 70 in f930280
Scoop/lib/manifest.ps1
Lines 132 to 154 in f930280
Considering that scoop buckets are a git repository anyway, why doesn't scoop first try to search the git history of the manifest file for the specified version?
This of course won't work in various scenarios, such as the version being older than it's scoop manifest, but the current approach also does not work in a lot of cases (often old downloads are linked on from a separate page, or the downloads history is paginated, ...). In case of failure, scoop could simply fall back to the current approach of generating the manifest.
Beta Was this translation helpful? Give feedback.
All reactions