• realharo@lemm.ee
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    1 month ago

    Native package managers were not “working fine for everyone”, the software and libraries in them are often very outdated and contain custom patches that don’t come from the original software authors.

    So you often end up dealing with bugs that were already fixed and the fixes released months ago.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 month ago

      That’s one of the main reasons I use a rolling release distro. I used Arch for years, and now I use Tumbleweed.

      With packaged apps (like flatpak, snap, etc), you can end up with outdated dependencies in those apps because they bundle everything together. So instead of fixing bugs once for everyone, you have to pester each individual package maintainer to update the dependencies. However, this is mitigated by having these apps be somewhat containerized and limiting impact of a breach on other apps, so YMMV depending on what kind of sandboxing you use.

      I’m not really decided here, and I use both flatpaks and distro packages. I don’t touch snaps though.

    • catloaf@lemm.ee
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 month ago

      That sounds like the maintainer’s problem, not a problem with apt/dnf/whatever. We’ve had automated build processes for decades. If you want stable, use a stable distro; if you want the latest, use a rolling release like Arch or something.

    • jonne
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      Other distros were faster with updating packages, or for Ubuntu specifically you had PPAs or repositories maintained by the vendor.