#How to use Winget?

1 messages · Page 1 of 1 (latest)

cedar lintel
#

I was not sure how Winget worked on the backend, but reading this helped. I noticed that it was last updated 5 days ago, with a "beta-9" tag, that does not exist. I understand its up to you all to update this manually, is this something that has fallen to the wayside to focus on other things or just a mishap?

south sentinel
upper ridge
#

So i want to start using winget, i use the command winget install --id=CiderCollective.Cider -e and it all seems to work fine, however its installing beta.415 when beta.417 is the latest one. Is there something I'm doing wrong or?

undone python
#

no

#

WinGet is just delayed because we have to manually update it

#

difficult to keep up

upper ridge
#

oh i see

#

makes sense

#

just wondering if its worth me using winget when i like updating Cider after every couple commits or continue self compiling

slim quest
#

it only makes sense to self compile if there is a specific change you'd like for yourself; besides that just stick to downloading via /branchbuilds

upper ridge
#

Winget seems faster than Branchbuilds even if downloading the exe from the website which is cool

south sentinel
south sentinel
upper ridge
#

yeah

#

it just opens a window and i dont have to click anything, it just starts installing right away

#

much faster than branchbuilds, downloading from the website and self compiling

#

only downside is its not updated with every commit, so i have to download from the website but even that is still faster

south sentinel
#

cuz "Quality Assurance"