Today, I’d like to announce Homebrew 5.0.0. The most significant changes since 4.6.0 are download concurrency by default, official support for Linux ARM64/AArch64, timescales for deprecating macOS Intel and removing macOS Gatekeeper bypass behaviours.
Shame on you, Homebrew, for effectively killing FOSS apps from casks.
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.
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.
How will these other solutions bypass Apples quarantine?
By doing what homebrew currently does when you pass the
--no-quarantineflag, which is callxattr.Note that I’d probably support removing
--no-quarantineif Apple’s notarization service was free.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).
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.
Talking about balance when google is using the same tricks to crush f-droid is not reading the room.
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.