self update #3

New Issue

adam · 2024-10-15T15:09:49-04:00

adam commented

2024-10-15 15:09:49 -04:00

get that config value of where to look for updates. Is there an update? download it, launch that one, kill self.

on startup, check if we're an update. If so, delete the previous installation.
also, if we're a service, update the service file to point at myself.

get that config value of where to look for updates. Is there an update? download it, launch that one, kill self. on startup, check if we're an update. If so, delete the previous installation. also, if we're a service, update the service file to point at myself.

adam added this to the 1.0 milestone 2024-10-15 15:09:49 -04:00

adam added the

enhancement

label 2024-10-15 15:09:49 -04:00

adam commented

2024-10-31 18:44:24 -04:00

nah fuck that.

ok i've been hemming and hawing on this for a while.

"when a new version exists, it'll be built by jenkins. you know, integrate your changes. Why not have it deliver them, as well? you know, both CI and CD."
"Don't have jenkins. Have it update itself. What if you had external users?"
"when. When am I going to have external users. fucking never. YAGNI."
"well, yes, I won't. but a business might. You know, the dudes who might offer a trade where you do this for them and they give you money."

and so, the dilemma: YAGNI vs Resume. Tough call, right? After all, I Ain't Gonna Need Shit, especially if I had the guts to flavor test a shotgun barrel. so... "decide on which futile quest for worthless ends to put your effort into. go on then." but I can't. who knows.

consider: how do people update their software? either it's at the company's place, and thus i should be good at having jenkins continuously deliver, or, they update it themselves. Think about it: for 99% of apps by quantity, either i do apt-get update when i'm damn good and ready, or it's cloud-hosted and I don't get to administrate, for better or worse.
When have I ever seen a self-updating app? back in ye olden days on windows (especially windows itself), or firefox. So either self-updating is an unwelcome anti-feature, or the software is targeted at people who have lost their "update later" privileges.

Consider also that Eligos is blocked from the wider internet - perhaps a bit overzealously. it can't reach gitea, and no one can ssh in to it. Updating eligos will always be manual.

So, fuck it. Fuck auto updating.

so, at last, a conclusion: Jenkins will build, and if it's a service, deploy. Everyone else can pull when they're ready. And if you really really want to be pro, learn to write apt/pamac/scoop packages.

nah fuck that. ok i've been hemming and hawing on this for a while. "when a new version exists, it'll be built by jenkins. you know, integrate your changes. Why not have it deliver them, as well? you know, both CI and CD." "Don't have jenkins. Have it update itself. What if you had external users?" "when. When am I going to have external users. fucking never. YAGNI." "well, yes, *I* won't. but *a business* might. You know, the dudes who might offer a trade where you do this for them and they give you money." and so, the dilemma: YAGNI vs Resume. Tough call, right? After all, I Ain't Gonna Need *Shit*, especially if I had the guts to flavor test a shotgun barrel. so... "decide on which futile quest for worthless ends to put your effort into. go on then." but I can't. who knows. consider: how do people update their software? either it's at the company's place, and thus i should be good at having jenkins continuously deliver, or, they update it themselves. Think about it: for 99% of apps by quantity, either i do `apt-get update` when i'm damn good and ready, or it's cloud-hosted and I don't get to administrate, for better or worse. When have I ever seen a self-updating app? back in ye olden days on windows (especially windows itself), or firefox. So either self-updating is an unwelcome anti-feature, or the software is targeted at people who have lost their "update later" privileges. Consider also that Eligos is blocked from the wider internet - perhaps a bit overzealously. it can't reach gitea, and no one can ssh in to it. Updating eligos will always be manual. So, fuck it. Fuck auto updating. so, at last, a conclusion: Jenkins will build, and if it's a service, deploy. Everyone else can pull when they're ready. And if you really really want to be pro, learn to write apt/pamac/scoop packages.

adam closed this issue

2024-10-31 18:44:24 -04:00

Sign in to join this conversation.