View Single Post
Old 10-28-2019, 03:58 PM   #93
MGlitch
Wizard
MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.
 
Posts: 2,855
Karma: 22003124
Join Date: Aug 2014
Device: Kobo Forma, Kobo Sage, Kobo Libra 2
Quote:
Originally Posted by NiLuJe View Post
@MGlitch: What's your usual workflow?

macOS has *always* quarantined downloaded binaries (well, at least since the GateKeeper days).

The usual least-annoying way to deal with it on unsigned binaries was not to double-click 'em, as that was hitting a GateKeeper wall even before Catalina, but to right-click > Open them, which lead to a different GateKeeper popup, one with an actually clickable "Open" button.

(c.f., this recap in the OCP thread, which also still includes older thumbnails for the Open with > Terminal approach for a .sh).

I can't check myself, as I haven't updated to Catalina (because ADE).
But it's my understanding that this should still work without having to mess with the System Prefs.

Granted, here, this is easier with a .script than a .sh (see the relevant issue).
I’ll set the patches then launch terminal cd to the patch folder, and using terminal open the .sh file by dragging and dropping it into terminal.

I’m not sure if that’s the proper way but it’s what I’ve done for as long as I’ve patched.
MGlitch is offline   Reply With Quote