Improve MacOS Installer Path Handling

Open
#1,661 8 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
macos, zsh
Domain
cli

Research direction

Start with the macOS package named quarto-1.0.37-macos.pkg and the installed /Applications/quarto/bin/quarto entry point; compare how Homebrew exposes quarto in /opt/homebrew/bin. Done when a standard Homebrew/pkg installation makes quarto discoverable in zsh without manual relocation or symlink setup.

Written by the indexing model from the issue text.

Description

bug installers

Hi,

First, thanks so much for making this wonderful tool. I've been an active RMarkdown user, while also working heavily with a VS Code and Python. I'm very excited to see there's a RMarkdown equivalent outside R ecosystem, finally.

I intend to use Quarto with only Python and VS Code on macOS. After using homebrew to install quarto, which is the same as installing with the quarto-1.0.37-macos.pkg file, my shell can't find quarto in the PATH.

$ quarto
zsh: command not found: quarto

After some digging, I discovered that quarto-1.0.37-macos.pkg installed quarto folder in /Applications. A simple solution would be adding Applications/quarto/bin into my PATH. However, what I believe is a more elegant solution is following other command line tool installations such as youtube-dl.

For whomever facing the similar problem and also uses homebrew on macOS, I moved /Applications/quarto to /opt/homebrew/Cellar/quarto. Then I added the symbolic link of quarto to /opt/homebrew/bin/ using the following command (you can also just create a symbolic link without moving):

ln -s /opt/homebrew/Cellar/quarto/bin/quarto /opt/homebrew/bin/quarto

Now my shell can successfully pick quarto up.

quarto
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from quarto-dev/quarto-cli

All issues in quarto-dev/quarto-cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.