Error installing CLI utility on macOS

[coreybutler]

Fenix 3.0.0

[coreybutler]

The installer is supposed to create a link to the CLI utility, but a few people have experienced this issue. To manually fix this, run

ln -s /Applications/Fenix.app/Contents/Resources/scripts/fenix /usr/local/bin/fenix
sudo chmod +x /Applications/Fenix.app/Contents/Resources/scripts/fenix

[ibillwilson]

On a brand new machine (set up 10 days ago) running Mojave (10.14.6), /usr/local/bin doesn't even exist.

[coreybutler]

@ibillwilson long shot.... but do you happen to know if /usr/local/bin is in the $PATH on a fresh install? It is my understanding that it exists in the path even though the directory is not physically present, but I don't have a means to check on a fresh install right now.

Creating the directory in the install is no problem, but if that directory is not in the PATH, it needs to be added.

[ibillwilson]

@coreybutler ... interesting, it's actually the first entry in $PATH.
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

[coreybutler]

Thanks @ibillwilson! Given that the filepath exists, I have an installer fix for this now. There are some other options I'm exploring too (which may ultimately be more robust), but knowing the PATH contains that filepath in a fresh install means the installer can at least create the directory (if it doesn't already exist), which should resolve the issue.

I'll close this issue once it is released.

[jochmann]

I suspect with the latest update (Monterey) Apple has introduced harsher installer penalties for unsigned software? I can't seem to run the installer, unfortunately.

translated error message ["The pkg cannot be installed because Apple cannot scan the package for malicious code." ...]

Do you plan to revisit the repository and make updates to Fenix to work with Mx-Silicone Macs? Or at least the installer? Would love to keep it around for its ease of use. Thx!