Search Criteria
Package Details: quarto-cli 1.9.36-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/quarto-cli.git (read-only, click to copy) |
|---|---|
| Package Base: | quarto-cli |
| Description: | Quarto is an open-source scientific and technical publishing system built on Pandoc |
| Upstream URL: | https://quarto.org/ |
| Licenses: | MIT |
| Conflicts: | quarto-cli-bin, quarto-cli-bin-pre-release, quarto-cli-git, quarto-cli-pre-release |
| Provides: | quarto |
| Submitter: | trap000d |
| Maintainer: | harrietobrien |
| Last Packager: | harrietobrien |
| Votes: | 7 |
| Popularity: | 0.065328 |
| First Submitted: | 2022-03-06 08:39 (UTC) |
| Last Updated: | 2026-03-26 22:59 (UTC) |
Dependencies (10)
- dart-sass
- deno (deno-gitAUR, deno-canary-binAUR, deno-stable-binAUR)
- esbuild (esbuild-gitAUR)
- lua-lpeg
- nodejs (nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogenAUR, nodejs-lts-iron, nodejs-lts-jod, nodejs-lts-krypton)
- pandoc (pandoc-static-gitAUR, pandoc-binAUR, pandoc-sile-gitAUR, pandoc-cli)
- typst (typst-gitAUR)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
- npm (python-nodejs-wheelAUR, npm-corepackAUR) (make)
- rust (rust-beta-binAUR, rustup-gitAUR, rust-gitAUR, rustup) (make)
Required by (3)
- python-great-tables (requires quarto) (make)
- python-great-tables-docs (requires quarto) (make)
- rstudio-desktop (requires quarto) (optional)
Latest Comments
1 2 Next › Last »
lahwaacz commented on 2026-03-28 08:08 (UTC)
Since 1.9.36-1 switched from build-from-source to just repackaging the official binary, the package should be renamed to
quarto-cli-bin. Oh wait, that package already exists... so please switch back to build from source.bgme commented on 2025-06-22 09:48 (UTC) (edited on 2025-06-22 09:50 (UTC) by bgme)
The line 30 need to be removed.
phel commented on 2024-12-13 18:29 (UTC)
Same here - the package seems to be almost empty after the build.
kbipinkumar commented on 2024-12-10 18:10 (UTC) (edited on 2024-12-10 18:22 (UTC) by kbipinkumar)
as of version 1.6.39-1 this package has following critical errors
once installed executing quarto by calling '/usr/bin/quarto' gives following error
checking ${pkgdir} also shows quarto executable not being present at the expected location
trap000d commented on 2024-09-24 00:54 (UTC)
I have to maintain all quarto packages only as dependencies of RStudio. Since I've retired from keeping rstudio-desktop, I would also drop quarto. Arch maintainers planned to move it from AUR to 'extra'. This might be a good occasion.
trap000d commented on 2024-06-06 07:53 (UTC)
Hi @cbrnr,
Indeed,
quarto-clilooks quite stable and predictable. So I'd be happy to move it to extra (though I'm not aware of details of this process).cbrnr commented on 2024-06-06 07:15 (UTC)
Now that 1.4 has been out for quite a while, I wanted to ask about the plan to migrate this package to [extra] – still any major blockers? It seems like they now use a fairly recent Deno version (for quarto 1.5 they use 1.41, not entirely sure about 1.4).
trap000d commented on 2024-01-23 19:54 (UTC)
Hi @damir,
Correct, 'stable'
quarto-clican be built only against pretty old deno version (<1.29). In the future if/when Quarto developers will announce new stable release (1.4.xyz) it should become buildable again.You have several options to override it: 1) Binary packages
quarto-cli-binandquarto-cli-bin-pre-releasehave all components bundled2) source packages
quarto-cli-pre-releaseandquarto-cli-gitare built with the most recent deno.3) Install old deno 1.28.x from repo archives (not the best idea, though)
damir commented on 2024-01-23 15:55 (UTC) (edited on 2024-01-23 15:56 (UTC) by damir)
cannot build against an existing deno:
alerque commented on 2023-12-05 09:40 (UTC)
I'd like to get this migrated to [extra] someday and am evaluating where it is at now. The build is pretty messy, but obviously a lot of that is the result of a messy upstream build process. I think we'll have to get it cleaned up a bit tighter before I migrate though. For example rather than removing junk in
package()after the fact, I think we'll need to patch the build to not produce the junk in the first place. Before I get two far down that road though can you comment on the current situation withdeno? Are version bumps to that package going to be a problem for this one down the road?1 2 Next › Last »