4 ms·

Don't use custom repos, use container technologies (e.g. Flatpak, Docker etc) to install applications, update the system regularly (at least once a week). Usua

Don't use custom repos, use container technologies (e.g. Flatpak, Docker etc) to install applications, update the system regularly (at least once a week). Usually broken distro upgrades I see are because people run "curl randomdomain.ck/totallysafescript.sh | sudo bash -" to install things or use custom repos.

omolobo 2y ago
In other words, you won't break your system if you keep the system installation pristine.
calvinmorrison 2y ago
container stuff breaks the MOST for me. The hooks into the subsystems invariably are not working correctly be it like xdg preferences or finding things that are global, its nice to package things into their own sandboxes but those sandboxes have not played well with my wider systems. I am still thankful for snap getting me recent copies of popular software on my aged debian installs however.
- ChocolateGod 2y ago
  can't speak for Snap other than the nightmare it is on non-Debian based systems, but not really had any issues with Flatpak.
  - calvinmorrison 2y ago
    My biggest issues are xdg, sound thru pulse, printer stuffs, things like that which have connections in snap but don't seem to work quite right.
binkHN 2y ago
I hate Flatpaks; they're bloated monstrosities and I only run them when I have no other choice. Outside of that, distribution package maintainers tend to do a good job and that is my preferred way of running programs.
79a6ed87 2y ago
This is why I like Arch's Pacman a lot, and the reason why I avoid Debian derivatives. That `totallysafescript.sh` could at least be inside of the package manager scope. Most of the times someone already did it, and published it to AUR. IMO the reason why there are so many people running random scripts in Ubuntu/Debian is due to how more difficult/inconvenient it is to get a dpkg .deb when compared to a PKGBUILD file. Same for MacOS, in which you have to either rely on Homebrew wizardry or just running the script
- ChocolateGod 2y ago
  > That `totallysafescript.sh` could at least be inside of the package manager scope. Most of the times someone already did it, and published it to AUR. The AUR is still not as good as proper package management and shouldn't be considered a stable or reliable method of software distribution at scale.

omolobo 2y ago

In other words, you won't break your system if you keep the system installation pristine.

calvinmorrison 2y ago

container stuff breaks the MOST for me. The hooks into the subsystems invariably are not working correctly be it like xdg preferences or finding things that are global, its nice to package things into their own sandboxes but those sandboxes have not played well with my wider systems. I am still thankful for snap getting me recent copies of popular software on my aged debian installs however.

ChocolateGod 2y ago
can't speak for Snap other than the nightmare it is on non-Debian based systems, but not really had any issues with Flatpak.
- calvinmorrison 2y ago
  My biggest issues are xdg, sound thru pulse, printer stuffs, things like that which have connections in snap but don't seem to work quite right.

binkHN 2y ago

I hate Flatpaks; they're bloated monstrosities and I only run them when I have no other choice. Outside of that, distribution package maintainers tend to do a good job and that is my preferred way of running programs.

79a6ed87 2y ago

This is why I like Arch's Pacman a lot, and the reason why I avoid Debian derivatives. That `totallysafescript.sh` could at least be inside of the package manager scope. Most of the times someone already did it, and published it to AUR. IMO the reason why there are so many people running random scripts in Ubuntu/Debian is due to how more difficult/inconvenient it is to get a dpkg .deb when compared to a PKGBUILD file. Same for MacOS, in which you have to either rely on Homebrew wizardry or just running the script

ChocolateGod 2y ago
> That `totallysafescript.sh` could at least be inside of the package manager scope. Most of the times someone already did it, and published it to AUR. The AUR is still not as good as proper package management and shouldn't be considered a stable or reliable method of software distribution at scale.