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?

  • poki
    29·
    6 months ago

    By default, Fedora Atomic envisions the following in regards to installing packages/software:

    • First, try the Flatpak.
    • If that doesn’t work, use Toolbx(/Distrobox).
    • If all else fails, resort to rpm-ostree.

    This works pretty fine, but isn’t perfect:

    • Flatpak has become pretty good for software with a GUI. However, while it can do CLI, it’s underutilized.
    • Toolbx/Distrobox has its merits, but not everyone enjoys consuming CLI through containers.
    • Besides the fact that installing all your CLI tools through rpm-ostree will negatively impact how fast you can update your system, it also requires you to (soft-)reboot before you can access the newly installed package (unless you enjoy living on the edge with --apply-live). This can be pretty cumbersome, especially if you’re in flow.

    Thus, the situation around CLI on Fedora Atomic became a sore to the eyes. Within the community, there were multiple attempts to tackle this problem:

    • Nix; For some time, this was the perfect solution. Unfortunately, in its current iteration, installing Nix on Fedora Atomic requires SELinux’ enforcing mode to be turned off. As turning enforcing mode off is unacceptable for uBlue’s maintainers, this was eventually dismissed.
    • Better tooling around Toolbx/Distrobox; There have been made some efforts in this regard, perhaps most notably Ptyxis. But, we’re not there yet. Though, some are hopeful of what podmansh will bring to the table.
    • Homebrew; It behaves as any other package manager used for installing packages from the repository on any Linux distro out there. Except, in this case, it’s exclusively utilized for CLI. Currently, it’s simply the most straightforward in use. You just have to teach people to replace their apt/dnf/ pacman with flatpak (for GUI) and brew (for CLI). Furthermore, it comes with a big and healthy repository. Finally, it utilizes technologies related to the ones found on Fedora Atomic.
    • systemd-sysext; This has only very recently been added to systemd. I wouldn’t be surprised if this will play a prominent role going forward. Though, I’m unsure if CLI will benefit most of it.
    • mogoh@lemmy.ml
      4·
      6 months 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
        5·
        6 months 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.

        • Bitrot@lemmy.sdf.orgEnglish
          81·
          6 months ago

          The flatpak packaging tutorial has you build a cli app, so anyone building one is likely aware.

          The real issue is invoking the commands. If you install a snap of top, you run top and it opens. If you installed a flatpak it wouldn’t be added to your PATH and even if you added the exports directory to your PATH you would need to remember to run org.gnu.top. Nobody wants to run some random flatpak run command all the time or create aliases for everything, so “flatpak isn’t for cli” becomes the mantra.

          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.

          • theshatterstone54@feddit.uk
            3·
            6 months 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!