Better documentation on how to install or get quarto

[cderv]

What would you like to do?

Give feedback or suggest an improvement

Description

We could documents better all installers our own already on the page and also community ones we know of, including docker image we build in this repo.

We don't have yet a page with all that I think, or it is incomplete and hidden.

Official installers:

The ones built in this repo:

• For OS available at: https://quarto.org/docs/download/
• For docker this is at https://github.com/quarto-dev/quarto-cli/pkgs/container/quarto

known ones

It would require a disclaimer that they are community maintained but still useful to share I think

Pip

• https://pypi.org/project/quarto-cli/

Conda

• https://anaconda.org/channels/conda-forge/packages/quarto/overview

Windows

• scoop install quarto
• scoop install quarto-prelease
• winget install --id Posit.Quarto
• choco install quarto

Linux

• https://aur.archlinux.org/packages/quarto-cli-bin

Mac

• https://formulae.brew.sh/cask/quarto

[mcanouil]

Isn't it what the following issue was about?

• Add installation guide for our downloadable bundle #4505

---

Somewhat related:

• Document how to maintain your Quarto version #5047

[cderv]

Yes thanks for linking to those ! They are indeed related. Slights variations to me, but definitely could be handled together.

[wlatendresse]

Yes thanks for linking to those ! They are indeed related. Slights variations to me, but definitely could be handled together.

... and in less than another threee years to come. :-) Just kidding.

Thanks for all those pointers.

In my opinion, such intergral information does not belong in any document that can (or can not) be found anywhere on the web (in case it is accessible), but should rather be an integral part of a (wrapper?) binary to make a media break impossible. An additional parameter could spit out all the necessary information and otherwise simply pass all arguments on to the main program. This seems like a clean approach, as it would not require any external sources to clarify a possible problem.

I know that this is a chicken-and-egg problem, but probably most people (without fear of compilers, interpreters and all the problems that lie within) for whom the offered solutions do not apply will fall back on the sources. Maybe this is the right (additional?) place for such information.

The pointer to the AUR maybe could habe saved me (and probably plenty of rather silent souls) a lot of time, too. And I really hope I am the only one though I doubt that.

[cderv]

In my opinion, such intergral information does not belong in any document...

Thanks for sharing your feedback, this is appreciated. However, I'm sorry but I don't think I fully understand what you are suggesting in place of better documentation. A flag on the binary that prints install info wouldn't help someone who can't build or install it in the first place — so I'm not sure how it replaces a documentation page.

The pointer to the AUR maybe could habe saved me (and probably plenty of rather silent souls) a lot of time, too.

I know about AUR because someone shared it in our discussion forum, but we can't document every community build because we simply don't know about most of them. We ship some installers from our CI (and recently added .deb and .rpm), but we can't support everything that exists out there ourselves. This is why the community steps in to maintain builds for specific systems — like AUR, or NIX. We know they exist, we help where we can, but we are not directly involved.

---

If you'd like to discuss or propose a new idea like the one above, could you open a thread in https://github.com/quarto-dev/quarto-cli/discussions rather than commenting on specific issues? We keep GitHub issues scoped to the work they were opened for, and Discussions is the right place for broader proposals. Hope you'll understand this maintainer perspective — thanks!