I need to upgrade ... I just need to get around to it.
But we digress.
I need to upgrade ... I just need to get around to it.
But we digress.
Well, upgrading end-of-life systems is kinda the main subject here I think
Not a fan of workarounds to be honest
Workarounds are the spice of life in IT's world
Yeah, but I don't need a new daemon running on my system to download code from Github.
Your argument is flawed, as Github and snap are essentially the same deal:
git
, GPLv2) to connect to a proprietary server (closed source service @ github.com);snap
, GPLv3) to connect to a proprietary server (closed source service @ snapcraft.io).Or, at least for the large majority of software there, you can download it with any web browser. Or you can use a number of alternate clients. And any of those clients will talk to any git server, so you could move to GitLab, Gitea, Phabricator, or whatever with pretty much zero disruption. And once you've downloaded it, you don't need any git-related software to run it (unless the software itself depends on git for some reason).
If I understand correctly, to run snaps, you need to have the snap daemon constantly running on your system. If that's correct, I think that represents a significant difference. I also understand that there is only one snap store, and only one snap client. So I'd need to install a special piece of software whose only purpose is to download software from only one source, that then needs a separate daemon constantly running on my system in order to run. So no, I don't think they're anything close to the same deal.
So, with all due respect to the certbot maintainers, I think I'll continue to recommend that folks who have certbot packages available through their distros continue to use those--at least if they're kept reasonably up-to-date. Snap sounds like far too much baggage to run a script.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.