You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scoop is a command-line installer for Windows. I wrote a following manifest that, once added to any of the Scoop's buckets such as Extras, would enable installing kmeans-colors via scoop install kmeans-colors.
When I update to a new major version like 0.7.0 or 1.0, will the autoupdate tag pick up that as the new base version? Or will that require a manual update of the manifest to the next version?
Otherwise, I'm generally in favor of letting more people use the tool if they find it helpful and the burden of maintenance seems minimal for me.
Yes, Scoop buckets have GitHub Actions that check for new versions (0.7.0 or 1.0 would be correctly recognized as newer than 0.6.0) and apply automatic updates to manifests according to the autoupdate fields. Manual updates would be needed only when new binaries are available or when there are alterations in naming schemes etc., but not for when new versions are released.
Thanks for positively responding, I will leave comments about how things go!
Scoop is a command-line installer for Windows. I wrote a following manifest that, once added to any of the Scoop's buckets such as Extras, would enable installing
kmeans-colors
viascoop install kmeans-colors
.I am writing this issue to learn about how you might feel about this before actually making a PR there!
The text was updated successfully, but these errors were encountered: