Shame on you, Homebrew, for effectively killing FOSS apps from casks.

  • brax@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    But I thought Mac was just Linux for people who loved to spend money… Seems on brand to me.

  • mumblerfish@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I never understood what a “cask” in the brew lanuage means. I just do installs and if the brew install instructions involves a cask I just do it. How do I figure out which packages this will have an effect on on my system?

      • Chaser@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        I don’t use Bazzite. But if you have any pro arguments for Brew, feel free to share them. Change my mind.

        • ianonavy@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          I don’t really have an opinion, just an observation that switching back to Linux for me did not take me away from Homebrew

    • chocrates@piefed.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      I’m stuck with it at work. Plus Linux usually sucks on Mac for a long time while drivers get written

    • stupidcasey@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      True but I desperately need no compatibility, closed source, AppleCare, expensive hardware, limited lifespan, lock in … What did you call it Linux?

      • TurboWafflz@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        It’s crazy how bad software compatibility on macos is. I used to assume it was about the same or slightly better than linux in that regard, but my attempts to help my friend play games on macos have almost entirely failed despite the fact that I have tons of experience playing games on linux since it’s always been my main os

  • Korne127@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    removing macOS Gatekeeper bypass behaviours

    dafuq? That’s basically the entire point

    So yeah, there will be a fork soon that’s just compatible with the casks. Luckily that is very easily to do / manage

  • piyuv@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    https://github.com/Homebrew/brew/issues/20755#issuecomment-3330984446

    In the end, the whole point of Gatekeeper is to protect end users as much as reasonable, and continuing to make it easy to bypass isn’t a good thing in my view.

    Whole point of Gatekeeper is Apple policing users’ devices. The security benefit is just a side effect. If anything, users need to be protected from Apple more than small time hackers.

    This is a shame. Big tech brain is affecting developers everywhere.

    Controversial opinion: best way to learn fire will burn you is to try and see. I personally learned a lot about computers by infecting my machine with a shitton of malware when I was a kid. Modern parents are very adamant on letting kids run free and learn stuff by themselves, why not apply the same logic to computers?

  • KoalaUnknown@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    Their explanation as to why:

    --no-quarantine is used to forcibly bypass Gatekeeper, which is a built-in macOS security mechanism. This is used to run unsigned/unnotarized applications.

    macOS Tahoe is the final release to support Intel systems, and last year Apple updated macOS runtime protection to make it harder to override Gatekeeper. Macs with Apple silicon also don’t “permit native arm64 code to execute unless a valid signature is attached”. Finally, we are ending support for all casks that fail Gatekeeper checks on September 1st, 2026.

    With the above in mind, it’s time to deprecate the --no-quarantine flag from brew. It intentionally bypasses macOS security mechanisms, which we already actively discourage. Deprecating now will give a decent lead time for users using it to come up with another solution or adjust their workflows.

    • arcterus@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      Deprecating now will give a decent lead time for users using it to come up with another solution or adjust their workflows.

      The adjusted solution/workflow: use something other than homebrew

        • arcterus@piefed.blahaj.zone
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          1 year ago

          By doing what homebrew currently does when you pass the --no-quarantine flag, which is call xattr.

          Note that I’d probably support removing --no-quarantine if Apple’s notarization service was free.

          • monogram@feddit.nldeleted by creator
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            Notarisation, free (as in beer) limits your ability to run your code that (Corporate) doesn’t like, making it inherently non free (as in freedom).

            • arcterus@piefed.blahaj.zone
              link
              fedilink
              English
              arrow-up
              0
              ·
              1 year ago

              Yes, but you can still compile the code yourself. It’s only problematic for binary distribution. This is basically a question of balancing security vs. freedom I suppose.

              • monogram@feddit.nldeleted by creator
                link
                fedilink
                English
                arrow-up
                0
                ·
                1 year ago

                Talking about balance when google is using the same tricks to crush f-droid is not reading the room.

                • arcterus@piefed.blahaj.zone
                  link
                  fedilink
                  English
                  arrow-up
                  0
                  ·
                  1 year ago

                  Difference is compiling an app from source for Android is not really feasible on Android devices, whereas doing so on macOS is literally built into the package managers for macOS and is generally pretty trivial beyond it taking more time.

                  Also, macOS doesn’t prevent you from running the apps entirely.

  • M.int@lemmy.zip
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    The unsigned (FOSS) Apps aren’t removed yet. They will be removed by 2026-09-01. Removing --no-quarantine before that seems counter productive. And quite frankly removing unsigned Apps at all seems like a stupid idea. Homebrew is a third party package mamager, why are they precapitulating to Apple?
    Third party taps (or are they fourth party?) will step in. You can run xattr -d com.apple.quarantine in the .rb file.

    Relevant links.

  • plz1@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    Heh, there goes Librewolf’s only sane updating mechanism. IIRC, the devs of that are vehemently against paying Apple the money to sign the code, and they also fail to provide their own updater. It was one of the main drivers behind my switch to Waterfox.

  • myfunnyaccountname@lemmy.zip
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    Of the like 30 things I have installed through brew, 1 is not signed. Do I agree with the change, no. But there are other options out there.

  • woelkchen@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    Homebrew could provide their own casks of FOSS applications, compiled on their infrastructure and signed by their key. It’s kinda what F-Droid does on phones.