macOS: First run/ fresh install does not add ghostty to PATH

[archcorsair]

Summary

When launching Ghostty for the first time on macOS, the ghostty binary is not added to PATH
The documentation doesn't appear to outline additional steps for macOS.

Expected

The ghostty command should be available in the terminal on first launch

Actual

Running the ghostty command in terminal does not work until it is manually added to your profile, in my case:

export PATH=$PATH:$GHOSTTY_BIN_DIR

Ghostty Versions Tested

• 0.1.0-main+5e001fcb
• 0.1.0-main+61aff898

[mitchellh]

As discussed in Discord, I think we should do this in the shell integration for now because I don't want to introduce a helper binary between login and the shell as noted in: zed-industries/zed#4827 (comment)

[discentem]

One possible alternative to shell integration and a helper binary is to distribute a .pkg for Ghostty that has a postinstall script which creates a symlink instead of or in addition to the .dmg and .zip file. I was thinking to submit a PR for this but wasn't sure where the best integration point -- Makefile, Github Action, build.zig etc. Is there any interest in this solution? If so, please let me know where the best integration point is.

Here's a preliminary example in my fork: https://github.com/discentem/ghostty/blob/9abe973a9a53e9a470302a7877075d9941a14605/Makefile#L30-L36

• This example uses https://github.com/munki/munki-pkg, with the build-info.yaml file as input
  • build-info.yaml also supports specifying a certificate for signing and notarization if desired, though not shown in my fork yet
• Before munkipkg would be ran the Ghostty.app is copied to the right place to be embedded in the pkg. This would be the outputted by a previous build step (see my question about integration points).

One major downside to munkipkg is that it would introduce a Python dependency during build time. However, everything munkipkg is doing under the hood could just be converted to a shell script if that's undesired.