theofficialgman

> Do you mean the update-check script is to compare link / deb version with the Github repo? > If yes, the updater probably already done it, it will compare...

yes the time it takes is dependent on the apt list command which is super slow (everything else takes less than 0.1seconds) I wasn't going to suggest doing it that...

asking apt for example is way way slow than asking dpkg for the same info... even a simple optimization cuts it down to 0.3 seconds on my end `[ "$(curl...

I'll show an example of what I have in mind once I get some more time

so here is a simplified example. lets take the box64 install script. it pulls directly from master and since the script doesn't change the user is left with an out...

yes that sounds like it might be on the right track... it could be handled in github actions even (not too hard to setup, I've similar stuff once or twice...

just documenting this here: you can do stuff like this to get the status output (and more info) for repos that have CI on github could be useful for only...

yeah this looks about right for what I had in mind for this type of github based install. the only really unstable part of this has to do with the...

the only "slow" part of the script for me is when you call the github api and there isn't anything you can do about that only takes 0.25 seconds to...

also btw, your script isn't good for apps that have pre-releases/betas because it grabs those too an example is webcord https://github.com/SpacingBat3/WebCord/releases which has betas you will have to do something...