Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Codesign MetaCall distributable #28

Open
FirePing32 opened this issue Sep 3, 2024 · 1 comment
Open

Codesign MetaCall distributable #28

FirePing32 opened this issue Sep 3, 2024 · 1 comment

Comments

@FirePing32
Copy link
Contributor

MetaCall installed via .pkg does not require code signing, but the MetaCall launcher extracted from the .tgz distributable fails due to an invalid code signature. All the MetaCall core files need to be manually verified to remove Gatekeeper warnings. The distributable must be notarized before distribution in the CI.

@viferga
Copy link
Member

viferga commented Nov 6, 2024

I found an alternative, we can use fallback to brew and build NodeJS and MetaCall from scratch, now I have replaced the Homebrew recipe in order to use prebuilt libnode from metacall/libnode repo, but we can provide an alternative method to build (through an environment variable or something like that), and use this as fallback when the computer has disabled the installation of unsigned software. Another option would be to just correct the problems with Homebrew recipe and PR it into Homebrew repo.

For reference:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants