3 ms·
> But it's disingenuous to declare that there's no need for them I didn't say there is no need for them. They are just horrible solutions. > I repeatedly reco
by tpoacher 4y ago
> But it's disingenuous to declare that there's no need for them
I didn't say there is no need for them. They are just horrible solutions.
> I repeatedly recommend that ordinary users do not install software from third party apt repositories unless they really really have to
Fair enough, I wasn't making the case for third-party repositories specifically; I was indeed making the case for distribution-curated repositories.
In general if a version of a particular piece of software in the distribution's curated repository is older than the version I require, what I'm saying is that I will generally go to the project's website "a la windows style", and either download whatever binary they provide, or preferably if possible compile from source. My misc-updates package then simply checks for available updates, which is the main functionality missing when manually installing packages.
Obviously this may not be the best solution for everyone else, but for my own needs I found it far more functional and usable than either flatpak or snap.
- rlpb 4y ago> what I'm saying is that I will generally go to the project's website "a la windows style", and either download whatever binary they provide, or preferably if possible compile from source. That is dangerous from a security perspective though. That third party binary, or your built binary, has permission to everything your user can, including exfiltration of your online banking sessions and so on. That's not appropriate in the modern computing environment. Apps that haven't otherwise been curated really need to be sandboxed, and if you have to go out of your way to arrange a sandboxed environment, well, that's what snaps do out-of-the-box, and we can't expect users to be able to stand that up manually any more than we can expect them to compile from source.