I’m admittedly yelling at cloud a bit here, but I like package managers just fine. I don’t want to have to have a plurality of software management tools. However, I also don’t want to be caught off guard in the future if applications I rely on begin releasing exclusively with flatpak.

I don’t develop distributed applications, but Im not understanding how it simplifies dependency management. Isn’t it just shifting the work into the app bundle? Stuff still has to be updated or replaced all the time, right?

Don’t maintainers have to release new bundles if they contain dependencies with vulnerabilities?

Is it because developers are often using dependencies that are ahead of release versions?

Also, how is it so much better than images for your applications on Docker Hub?

Never say never, I guess, but nothing about flatpak really appeals to my instincts. I really just want to know if it’s something I should adopt, or if I can continue to blissfully ignore.

  • Shareni
    1·
    1 month ago

    Ok, show me how you compile Emacs 29/30 on a fresh Debian 10 install in a few minutes…

    • gandolfini_the_grey@lemm.eeEnglish
      1·
      1 month ago
      apt install build-essential
apt build-dep emacs
wget https://ftp.gnu.org/gnu/emacs/emacs-30.1.tar.xz
tar -xf emacs-30.1.tar.xz
cd emacs-30.1
./configure —prefix=/usr/local
make
make install

      Edit: forgot cd

      • Shareni
        11·
        1 month ago

        Did I ask for a command? Give that a try in Debian 10…

          • Shareni
            1·
            1 month ago

            No missing/outdated/renamed dependencies while building it?

            • gandolfini_the_grey@lemm.eeEnglish
              2·
              1 month ago

              Nope, a lot of software will try to bundle as much dependencies as needed by default, which makes building from source much easier. Distributions will then “unbundle” them, to keep packages reusing system libraries as much as possible