Appimage for me ticks all the boxes for cross distro package as its very portable, simple to run, what are devs trying to do when creating snaps and flatpack?

  • Avid Amoeba
    arrow-up
    6
    arrow-down
    0
    ·
    10 months ago
    link
    fedilink

    Software deployment that tackles dependency hell in a secure fashion while providing, repeatable, atomic upgrades and rollback.

    • rutrumEnglish
      arrow-up
      1
      arrow-down
      0
      ·
      10 months ago
      link
      fedilink

      Can you elaborate on update system? AppImage is just a format, right? Whereas flatpak is a format and an entire toolkit for downloading and running flatpaks.

      • Avid Amoeba
        arrow-up
        5
        arrow-down
        0
        ·
        10 months ago
        edit-2
        10 months ago
        link
        fedilink

        You already said it. Flatpak and Snap both include an entire system around updates and rollback which provide some pretty strong guarantees for update success. AppImage does not. It’s got some libs available that an individual developer could use to implement their own update mechanism but isn’t a built-in. And besides, without a system-level component that manages install/update/rollback, you can’t have any guarantees about the update process. You’re back to the Windows-world per-app update.exe paradigm (or update.sh in Linux).

    • MonkderZweite
      arrow-up
      0
      arrow-down
      0
      ·
      10 months ago
      link
      fedilink

      There’s software for that. Honestly, i prefer that over the ‘whole package or nothing’ approach in Flatpack, which still has ~/.var for packages hardcoded btw.