We should seek to minimize the impact that setting up Obelisk has on the end user's local filesystem.
We should minimize the system-level development dependencies as much as possible by moving deps into pixi when we can.
However, we should make sure that if the end user doesn't want to use pixi, there is a clear way for them to do so.
Some notes on this front
mesa-common-dev seems hard to eliminate. We can build the glfw-related packages in pixi by specifying glfw and mesalib as conda dependencies, but we ultimately cannot open the glfw window without locally installing mesa-common-dev.
We might be able to eliminate libyaml-dev as a system-level dependency, but we haven't investigated this thoroughly on the conda side.
The setup script and pixi tasks currently add a lot to the user's bashrc. We may want to consider adding all these things to a separate file that the end user can choose to source temporarily but is sourced automatically by pixi to reduce the impact we have on the end user's settings.
We should seek to minimize the impact that setting up Obelisk has on the end user's local filesystem.
mesa-common-devseems hard to eliminate. We can build theglfw-related packages inpixiby specifyingglfwandmesalibascondadependencies, but we ultimately cannot open theglfwwindow without locally installingmesa-common-dev.libyaml-devas a system-level dependency, but we haven't investigated this thoroughly on thecondaside.