• 5 Posts
  • 214 Comments
Joined 1 year ago
cake
Cake day: August 3rd, 2023

help-circle





  • Basically installing packages. You’re fine if you default to using

    • flatpaks for gui apps
    • brew for cli programs
    • distrobox when building from source or when you need good control over the package environment (e.g. when installing a latex editor and only the latex packages you want)
    • layer packages on host with “rpm-ostree install” when the program needs tight integration with the host (e.g. VPN software)

    Also, you shouldn’t edit files in /usr, but I’ve never run into that limitation. You can still edit other top-level directorys like /etc .

    That’s about it.



  • jack@monero.towntolinuxmemes@lemmy.worldIf we had parties
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    7 months ago

    Yes, the first flatpak is big cause you have to download the runtime (most common dependencies you will probably need anyways in the future). The majority of other flatpaks you will download will use the runtime you’ve already downloaded so those flatpaks will be lighter than the appimage variant




  • You should definetely check out Bazzite, it’s based on Fedora Atomic and has Steam on the base image. Image and Flatpak updates are applied automatically in the background, no need to wait for the update on next boot. Media codecs and necessary drivers are installed by default.

    The Bazzite image also directly consists of the upstream Fedora Atomic image, just with quality of life changes added and optimized for gaming



  • Noob question?

    Should I’ve made a new post instead?

    You do seem confused though… Debian is both a distribution and a packaging system…

    Yes, Debian is a popular distro depending on Debian packages. My concern is about the update policy of the distro

    But the whole reason debian-based distros exist is because some people think they can strike a better balance between newness and stability.

    Debian is pure stability, not the balance between stability and newness. If you mean debian-BASED in particular, trying to introduce more newness with custom repos, I don’t think that is a good strategy to get balance. The custom additional repos quickly become too outdated as well. Also, the custom repos can’t account for the outdatedness of every single Debian package.

    you seem to be throwing the baby out with the bathwater… the debian packaging system is very robust and is not intrinsically unlikely to be updated.

    Yes, I don’t understand/approve the philosophy around the update policy of Debian. It doesn’t make sense to me for desktop usage. The technology of the package system however is great and apt is very fast