• nitrolife@rekabu.ru
    link
    fedilink
    arrow-up
    5
    ·
    6 hours ago

    Provided that flatpack has a common parent container, which is not always the case. More precisely, it almost never does. Because someone updates flatpack to new versions of the parent containers, and someone else does not.

    • grinka@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 hours ago

      More precisely, it almost never does.

      I don’t know any flatpak in my system that don’t use runtime (I have around 50 flatpak apps installed), or am I misunderstanding your point

      • nitrolife@rekabu.ru
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        5 hours ago

        runtime have versions too. If one runtime version use only one flatpack than exactly same as just static linking binary. Flatpack have just docker layeredfs and firejail in base.

        id: org.gnome.Dictionary runtime: org.gnome.Platform runtime-version: '45' <- here sdk: org.gnome.Sdk command: gnome-dictionary

        • grinka@lemmy.zip
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 hours ago

          I see problem in that only in unmaintained apps (like org.gnome.Dictionary), I have only GNOME 47 & 48 for example and both of them still updating

          • nitrolife@rekabu.ru
            link
            fedilink
            arrow-up
            4
            ·
            5 hours ago

            In the initial stage of shared library support, everything was exactly the same. Let’s look at it in 5 years… When some soft will archived and die, some stop maintaining, some new crated and brakes old dependencies…