3 ms·

To ensure snap will not be installed again see the apt config here: https://github.com/cies/kubuntu-setup#remove-snap https://github.com/cies/kubuntu-setup#rem

by cies 7y ago

To ensure snap will not be installed again see the apt config here: https://github.com/cies/kubuntu-setup#remove-snap https://github.com/cies/kubuntu-setup#remove-snap This is needed because an every growing number op packages is "dependant" on it. Here I show how to install Chromium as a DEB package from Debian (on a buntu): https://github.com/cies/kubuntu-setup/tree/master/chromium https://github.com/cies/kubuntu-setup/tree/master/chromium

madars 7y ago
Chromium is actually the only real use case for snaps. It is so difficult to build/package chromium for a LTS distro that Debian simply stopped trying. See what happens with security updates on Debian jessie (which is under their LTS): https://security-tracker.debian.org/tracker/source-package/chromium-browser https://security-tracker.debian.org/tracker/source-package/c... . Ubuntu made the right choice here: https://snapcraft.io/blog/chromium-in-ubuntu-deb-to-snap-transition https://snapcraft.io/blog/chromium-in-ubuntu-deb-to-snap-tra...
- Avamander 7y ago
  It's a terrible use-case that causes data loss for users, for FOUR years now: https://bugs.launchpad.net/snapd/+bug/1616650 https://bugs.launchpad.net/snapd/+bug/1616650 I despise the bug, it causes so much trouble without a way to turn it off. Plus the switch to snap happened exactly during a critical vuln which meant people were running on critically vulnerable chromium for weeks.
- Taniwha 7y ago
  Except that chromium under snaps is pretty unusable unless your home directory is structured exactly the magic way Canonical expects, if you have symbolic links, stuff on other disks, suddenly you can't upload your customer orders, or your PCB CAD designs to be made, you can't save files into /tmp anymore, even if you've been doing that for 3 decades. And it all fails silently, mysteriously, no error messages explaining why stuff has suddenly stopped working. I'm not against stuff changing, but tell us up front, explain what's changed and make sure that you're not breaking existing things or provide a way for people to keep their existing stuff work, a flag that says that following symbolic links is OK ... and put that UI in Chromium itself, not in some other box somewhere

by cies 7y ago

madars 7y ago

Chromium is actually the only real use case for snaps. It is so difficult to build/package chromium for a LTS distro that Debian simply stopped trying. See what happens with security updates on Debian jessie (which is under their LTS): https://security-tracker.debian.org/tracker/source-package/chromium-browser https://security-tracker.debian.org/tracker/source-package/c... . Ubuntu made the right choice here: https://snapcraft.io/blog/chromium-in-ubuntu-deb-to-snap-transition https://snapcraft.io/blog/chromium-in-ubuntu-deb-to-snap-tra...

Avamander 7y ago
It's a terrible use-case that causes data loss for users, for FOUR years now: https://bugs.launchpad.net/snapd/+bug/1616650 https://bugs.launchpad.net/snapd/+bug/1616650 I despise the bug, it causes so much trouble without a way to turn it off. Plus the switch to snap happened exactly during a critical vuln which meant people were running on critically vulnerable chromium for weeks.
Taniwha 7y ago
Except that chromium under snaps is pretty unusable unless your home directory is structured exactly the magic way Canonical expects, if you have symbolic links, stuff on other disks, suddenly you can't upload your customer orders, or your PCB CAD designs to be made, you can't save files into /tmp anymore, even if you've been doing that for 3 decades. And it all fails silently, mysteriously, no error messages explaining why stuff has suddenly stopped working. I'm not against stuff changing, but tell us up front, explain what's changed and make sure that you're not breaking existing things or provide a way for people to keep their existing stuff work, a flag that says that following symbolic links is OK ... and put that UI in Chromium itself, not in some other box somewhere