I run Debian 13 Stable with KDE Plasma, and have Flathub enabled on KDE’s Discover software store. I have a slight idea of the difference between the two: that Debian packages share system libraries and are therefore lighter in storage but do require password to access those shared libraries and could therefore become a security hazard if installing from an untrusted source, while Flatpaks have all they need and don’t require password to install, being more secure that way, but, as a consequence, consume more storage. Also noticeable is the fact that, for some programmes, the Flatpak version tends to be more recent and it therefore becomes the obvious choice when looking for the latest software.

However, I was looking at the SuperTux game, and what’s curious about this is that both, the Debian package and the Flatpak are version 0.6.3, while consuming 6.7 and 259,9 MB of storage respectively.

So should the obvious choice here be the Debian package, or would you still go for the Flatpak? I am not asking this because I’m particularly interested on this game as much as to learn more about the two system packages and whether my assumptions are correct or I am missing something.

Thank you and have a nice weekend!

  • 0t79JeIfK01RHyzo@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 days ago

    Sometimes it’s specific to the application. As an example, yt-dlp is redistributed by Canonical, and they usually maintain stable packages, but their versions seem to lag like 6 months. This might be related to their desire for stability, or maybe just align to their release cycle. I don’t know.

    The issue is that yt-dlp needs to be updated more frequently because websites break their methods of downloading, so the version that follows the latest version seems to work better.

    I don’t think using PPA’s is usually recommended, (like in the photo) so I think I would recommend flatpaks first if the developer of the application maintains one themselves. (and you want to follow later releases.) Though, the first time I had to use flatseal to fix an application, I felt like flathub was a failed platform.

  • juipeltje@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    5 days ago

    Usually native packages are preferred, unless like you said you want a newer version. Some people also like the sandboxing that flatpak does if you don’t fully trust a program. The reason why the flatpak is so much bigger is because it needs to download the dependencies as well, because it can’t use the ones on your system. In this case since it’s a game it probably needs graphics drivers as well, which are fairly big i think.

  • Pika@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    5 days ago

    I run Debian 13 and I will use apt repositories whenever possible and I avoid flatpak with a passion.

    My flowchart is:

    1. App Image if the application supports auto updating or if it’s a temperary app
    2. Apt repository
    3. Deb file
    4. App Image (when previous didn’t apply)
    5. Source
    6. Flatpak

    My main reasoning for it is strictly ease of use. I find flatpaks while I’m sure makes it easier on the developers making it to be super bloaty and take up more system resources, While causing more restrictions and annoyances during configuration due to their enhanced security setup.

    The only time I really don’t use a repo if it’s available is if the program itself updates on its own, or updates super frequently such as Discord, which I got annoyed enough at that I had to make my own update script that to check if there’s an update and then auto update it, because I got sick of the Discord has an update message every other day.

  • pastermil@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    5 days ago

    Of course it would require password, you’re putting something into your system after all. Arguably, Flatpak has some layers between it and your inner system.

    What di you mean your distro’s repo is an untrusted source? Did you do something funny to it?

  • Paragone@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 days ago

    IF the distro’s .deb is recent-enough, THEN go with that.

    IF it’s generations out-of-date, then you may have no choice but to go with the flatpack.

    OS-integration ( with apt, for the .deb ) is to be preferred, generally.

    _ /\ _

  • utopiah@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    5 days ago

    Heuristic : if you don’t know, trust your distribution. If you don’t trust your distribution, pick another one, repeat.

  • BrianTheeBiscuiteer@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    5 days ago

    You might also consider linuxbrew as well, depending on your goals. AFAIK it’s almost the same as native but with better separation of dependencies.

  • Cryxtalix@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    5 days ago

    My personal rule of thumb is that if it interacts with the OS or filesystem deeply, native is probably better. E.g. IDEs, cli programs, browsers, Steam etc.

    Apps that do a simple things are likely to work perfectly fine on flatpak.

    But the problem is that there are outliers in each case. You should pick one and be ready to switch if things don’t work properly.

    • Archr@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 days ago

      This is effectively how I judge it as well. Only thing I would add is that more things can be Flatpaks (ie. Steam). As long as you know about and use Flatseal to change the permissions. For instance, giving Steam access to my games directory.

    • somethingDotExe@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 days ago

      This ^^ my rule of thumb is always using the zypper packages (I’m using openSUSE TumbleweedOS) I had troubles with some flatpacks before, but only one! It was enough for me to not return though xD still use flatpacks but only for less important apps. Not for steam, wine, etc.

  • fizzle@quokk.au
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 days ago

    For desktop things, appimage is my preference. Then flatpak then debian repo.

    For cli things, if its a really old school low level utility then debian repo, otherwise nix.

      • fizzle@quokk.au
        link
        fedilink
        English
        arrow-up
        0
        ·
        5 days ago

        Not really, just my anecdotal experience of which package systems are most reliable.

        AppImages seem to be the most likely to be directly supported by project maintainers. Flatpaks seem to be third party.

        Nix is a great package manager but I haven’t had much luck with desktop applications from nix.

  • hendrik@palaver.p3x.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 days ago

    I’d go with the Debian package. That’s tied into the system. You get nice updates, there’s more eyes on what the upstream developers do, sometimes the Debian maintainers disable things like tracking, fix vulnerabilities in libraries. It’s smaller, less permission issues… It’s just safer and more convenient…

    I’ll go for Flatpak once there’s some benefit. For example the sandboxing which is great to have for proprietary software. Or if the package isn’t available in the Debian repositories, and the alternative would be some third-party repo or deb file downloaded from a random website.

  • Alex@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    5 days ago

    Stable package > back port package > flatpak/snap.

    Basically I want everything as stable as possible unless I have a particular need for a newer feature.

    The main things I run from flatpak/snap are browsers and the Minecraft launcher because they are both regularly updated.

  • Emma_Gold_Man@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    0
    ·
    5 days ago

    Before going to Flatpak just for newer versions of software, consider APT pinning. You can actually use testing or Sid packages on more stable versions of Debian while still keeping the advantages of Debian-specific packages.