Manuel Kaufmann

We should probably add Ruby to "build.tools" options. There is no reason to not have it there

@henryiii BTW, you could solve your immediate issue by doing something like: ```yaml build: commands: # Install Ruby using "asdf" - asdf plugin add ruby https://github.com/asdf-vm/asdf-ruby.git - asdf install ruby...

Glad the yaml snippet helped here. #10346 will improve the download/compiling time spent on Ruby. We cannot cache package/gem installation, tho, but at least the compiling time will be saved....

> I think it will be hard for us to feel good about implementing a sudo layer for build.commands usage, so there is a more obvious path in making `build.jobs`...

Gotcha! I think for a lot of cases `build.jobs` will be enough and I will be happy recommending that to most of our users. However, installing a OS package with...

@ssbarnea we have a `git-lfs` example in our documentation that does not require installing packages with APT: https://docs.readthedocs.io/en/latest/build-customization.html#support-git-lfs-large-file-storage. Can you try that and let me know if it works for...

@ktbarrett the thoughts/patterns behind this decision are: * `build.jobs` allows users to quickly setup their project and assist them with the default commands that have to be executed for Sphinx...

> What I'm saying is that a solution achievable _now_ would be a separate feature that would allow the user to override the `build` stage in `build.jobs` (currently you can...

I think this issue is deviating a little from its original purpose at this point. @agjohnson that workflow probably works for most of the Python doctools. However for any non-Python...

Just want to make a note here that we are re-writing these javascript (mainly, readthedocs/core/static/core/js/readthedocs-doc-embed.js) completely in https://github.com/readthedocs/addons and this problem should be fixed once we roll it out more...