Arvados

Brett Smith wrote:

1. Install without privileges: Probably break this up into subsections to go from what most people will find easiest vs. hardest. Explain what you get at each step and let users know they can jump off whenever.

I'm starting to think it doesn't make sense to do this in the abstract, because realistically you'll need privileges to install build tools and headers for curl and FUSE. At that point, the instructions are so much more complicated for such a narrow use case, I don't think the effort is justified.

What might make sense is a higher-level generic "how to add Arvados Python packages to your development environment." But then it probably makes sense to have that documentation in the Python package(s) specifically, rather than this generic "setup client tools" page.

21572-user-packages @ c053155a074d202cc4a52a4a5829bd0083a3a69f - developer-run-tests: #4282

• All agreed upon points are implemented / addressed.
  • More or less, see the caveat above
• Anything not implemented (discovered or discussed during work) has a follow-up story.
  • N/A
• Code is tested and passing, both automated and manual, what manual testing was done is described
  • See above. Also tested the install instructions by hand in Docker containers of focal (the oldest deb-based distro we support) and Rocky 8.8.
• Documentation has been updated.
  • Yes
• Behaves appropriately at the intended scale (describe intended scale).
  • N/A for a pure documentation branch
• Considered backwards and forwards compatibility issues between client and server.
  • Ditto
• Follows our coding standards and GUI style guidelines.
  • N/A (no documentation style guide)

This makes it a lot less cumbersome. LGTM, thanks!