• Ephera@lemmy.ml
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    2 months ago

    Sure, but presumably AppImage/Flatpak/Docker cannot help with that either…?

    • henfredemars@infosec.pub
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 months ago

      This is the problem those tools try to solve. They package everything else upon which software might depend that can’t simply be linked into a single binary.

    • ryannathans@aussie.zone
      link
      fedilink
      arrow-up
      3
      ·
      2 months ago

      Flatpak solves the problem with targetable platform versions, you just update the manifest for your app every like 6-12 months to target the new one

      • Ephera@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        Ah, interesting. So, it’s different from just statically linking against the latest driver lib every 6-12 months, because the Flatpak runtime gives you a bit of a guarantee that there won’t be breaking changes in the meantime.

        • ryannathans@aussie.zone
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          2 months ago

          Bingo, and if the latest mesa breaks your app for example, you can target an older one until it’s fixed instead of end users having to fuck around downgrading system packages