It may be Apple policy to prevent users from doing what they want because "security" is the most important thing for a their bank/shopping terminals. But I thought the whole point of using homebrew was to empower the user to use Apple devices like a normal computer without the hassle of having to do it manually? The developer has made it clear this is not the use case and that it helped with it was unintentional and undesired. The actual use case for homebrew remains unclear given this new information.

▲

nemothekid 9 hours ago | parent [-]

As I understand it `--no-quarantine`, as it is currently implemented, is a noop on ARM Macs. So if Homebrew has two options:

1. Play cat and mouse with Apple to ensure `--no-quarantine` works

2. Deprecate and remove the feature.

▲

saagarjha 5 hours ago | parent | next [-]

No, it definitely has an effect on Apple silicon. Without this you will be blocked from running ad-hoc signed code.

▲

superkuh 9 hours ago | parent | prev [-]

Well, 2. is what the people are asking for but aren't getting. They want deprecation and a ENV flag to enable. It'd be enough. But even that isn't being allowed which is weird for a power-user program. I can't help but think, "Don't obey in advance."

	▲	nemothekid 8 hours ago \| parent [-]
		2 is what is happening. The feature is being deprecated and will likely be removed in the next MacOS version. >I can't help but think, "Don't obey in advance." They aren't obeying in advance. They simply aren't doing the work to find another Gatekeeper bypass for ARM64.