Idea #21573
Updated by Brett Smith 2 months ago
We build a lot of individual packages that are basically just remnants of older versions and build processes of Arvados, and serve no functional purpose. We could migrate to this much simpler set. This would reduce build times, simplify install instructions, and take less space on installed machines. * @arvados-server@: The As now, the @arvados-server@ binary, configuration files, documentation, and symlinks in @/usr/bin@ for all the different names you can call it by * @arvados-client@: The same thing for the @arvados-client@ binary * @arvados-python-client@: A single venv with the PySDK, a-c-r, arv-mount, crunchstat-summary, and user-activity all bundled. * @arvados-python-compute-node@: A single venv with arv-mount and docker-cleaner all bundled. We would need to think about how to handle the arv-mount conflict. If Crunch could learn to call it directly from this venv, that would help. Worst case, we could just declare the venv packages conflict with each other, I'm not aware of anyone who wants to install both on the same system. * @arvados-api-server@, @arvados-workbench2@, @arvados-src@, and @libpam-arvados-go@ remain as they are now, as well as any other little utility tools I overlooked.