The quarto for Linux tarball works on macOS, how come? #6641
-
DescriptionHi all disclaimer: I have 0 experience with macOS so maybe my question is very obvious. I am trying to package quarto for Nix for macOS. Nix is a package manager that works on Linux, Windows with WSL2 and macOS. For now, quarto on Nix is only available for Linux, and I wanted to help package the macOS version. So I was wondering: is this expected behaviour? What are the differences between the Linux and the macOS tarballs? I’ve also discussed with @cderv on the French R users Slack about this, and was wondering if the next release of quarto (1.4) will have an intel and apple sillicon specific tarballs? Cheers |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
(my disclaimer I don't know anything Nix) I think you have it slightly wrong, and what's happening is that the nix linux tarball works on macOS, because whoever packaged that is not shipping any of the binary dependencies. Our tarballs ship binary dependencies with them, and so are (clearly) dependent on architectures. |
Beta Was this translation helpful? Give feedback.
-
Ok I think I got it. After your answer I tried the Linux tarball on my hackintosh vm (without nix), and Thanks for helping me see! |
Beta Was this translation helpful? Give feedback.
(my disclaimer I don't know anything Nix)
I think you have it slightly wrong, and what's happening is that the nix linux tarball works on macOS, because whoever packaged that is not shipping any of the binary dependencies. Our tarballs ship binary dependencies with them, and so are (clearly) dependent on architectures.