What’s up with homebrew that you’d have it installed by default on linux?

I don’t understand the appeal of it, can someone help me?

  • mogoh@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    2 years ago

    Very interesting. I wish flatpak would offer a better CLI experience. I don’t want another package managing tool, but here we are.

    • poki@discuss.online
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      2 years ago

      Can’t agree more.

      I believe Flatpak initially couldn’t and/or didn’t want to do CLI. At some point, it offered some basic functionality; I first noticed it on Bottles. But, it’s pretty dire if no variation of top can be found as a Flatpak.

      I wouldn’t be surprised if most people are simply unaware that Flatpak can even do CLI. This inevitably also negatively affects its CLI ecosystem.

        • theshatterstone54@feddit.uk
          link
          fedilink
          arrow-up
          3
          ·
          2 years ago

          In an ideal world a flatpak could register the cli commands it wants to present to the user, and some alternatives system could manage which flatpak gets which command if there were collisions.

          This has been my dream ever since I discovered Flatpak. I wish it becomes the case one day.

          It’s good that there has been partial progress in that direction. Let me give an example with the Floorp browser. I can do a flatpak install floorp and I can do a killall floorp and they will work. If we can somehow get a way of accessing flatpaks as if they’re regular packages via the terminal (is it possible to build a program to do this and have it packaged as a flatpak?; Maybe a program that creates a oneliner script to act as an “alias” in a directory (within $HOME so it works on immutable systems) that gets added to $PATH), that would be amazing!