v1.0.0 darwin x86 binary cannot be run right away as dev can't be verified

[balupton]

“sd” cannot be opened because the developer cannot be verified.

doing the right-click open trick makes it work from then on, however I'm unsure of any programatic way of doing that

[balupton]

Okay the trick is xattr -d com.apple.quarantine ...

[NoahTheDuke]

If you open your privacy and security settings, there will appear a password-protected button to let you run the app even tho it's not verified.

[CosmicHorrorDev]

Thanks for opening the issue. I'll have to poke around and see what all is needed to handle signing the binary

[coolaj86]

Perhaps adding an install.sh that

• moves the package into ~/.local/opt/sd/ or ~/.local/{bin,share}
• runs xattrs on Darwin (macOS)
• echos the line to add to PATH to put in the shell

[nc7s]

Kindly consider using Homebrew or MacPorts or nix-darwin. Tarballs aren't really a good way to install CLI programs.

[coolaj86]

I also just updated https://webinstall.dev/sd for the v1 package structure.

(it uses your uname -srm output to match the correct build for your system and then the download from GitHub happens directly from your terminal - avoiding the need for 500mb of unrelated git history or 50mb of package management history just to download a single file)

[balupton]

Kindly consider using Homebrew or MacPorts or nix-darwin. Tarballs aren't really a good way to install CLI programs.

Those tools use the tarball.

For myself, the tooling is Dorothy, which now dequarantines bins:

https://github.com/bevry/dorothy/commit/cc23edba83288fb2f66c36c8296704ba15a4e8ab

[nc7s]

Those tools use the tarball.

With, quote, "500mb of unrelated git history or 50mb of package management history". They are complete software package management systems, with features including but not limited to, file hash verification, installation steps tailored to the OS, etc.

But you are right to use anything you like. I shouldn't and won't waste more time on this topic.