Deprecate usage of OpenGL utilties and NixOS options.

[jonringer]

The /run/opengl-driver/ directory contains more than just opengl libraries now. It also includes vulkan implementations, machine learning libraries, hardware-accelerated encoding and decoding, opencl implementations, and many others. Directory renaming is now out of scope

This directory is also being used as the way to get access to the host machines gpu drivers. I think it's another source of confusion for many users to have to add addOpenGLRunpath so that they can get a vulkan game / cuda workload / opencl workload to work.

I think we should deprecate this prior to the 21.11 release, and fully move it to something like /run/gpu-driver/ or something more representative of the desired affect.

I would also like if someone specifies a value for services.xserver.videoDrivers, that they would also get the gpu libraries mounted automatically instead of needing to do a separate hardware.opengl-drivers.enable = true;. This was done in 02cef04c8187

cc @ryantm

EDIT: roadmap (2.5 years later... lol):

• addOpenGLRunpath -> addDriverRunpath

  • Init addDriverRunpath: addDriverRunpath: init #269475
  • Deprecate addOpenGLRunpath cudaPackages.addDriverRunpath: cudaPackages: generalize and refactor setup hooks #281576

• autoAddOpenGLRunpathHook -> autoAddDriverRunpath

  • Init autoAddDriverRunpath: autoAddDriverRunpathHook: init #297212
  • Deprecate cudaPackages.autoAdd{OpenGLRunpathHook,DriverRunpath}:
    • dcgm: use pkgs.autoAddDriverRunpath #300277
    • lammps: use pkgs.autoAddDriverRunpath #300278
    • sunshine: use pkgs.autoAddDriverRunpath #300287
    • openai-whisper-cpp: use pkgs.autoAddDriverRunpath #300288
    • colmap: use pkgs.autoAddDriverRunpath #300290
    • btop: use pkgs.autoAddDriverRunpath #300292
    • ucx: use pkgs.autoAddDriverRunpath #300293
    • xgboost: use pkgs.autoAddDriverRunpath #300294
    • cudaPackages.nccl: use pkgs.autoAddDriverRunpath #300295
    • cudaPackages.saxpy: use pkgs.autoAddDriverRunpath #300296
    • jaxlib-bin: use pkgs.autoAddDriverRunpath #300297
    • python3Packages.jaxlib: use pkgs.autoAddDriverRunpath #300298
    • tabby: use pkgs.autoAddDriverRunpath #300299
    • llama-cpp: use pkgs.autoAddDriverRunpath #300300
    • python3Packages.tensorrt: use pkgs.autoAddDriverRunpath #300301
    • python3Packages.torch*: use pkgs.autoAddDriverRunpath #300302
    • cudaPackages.autoAddX: Deprecate #300321

• NixOS Module changes: TODO @Atemu?

[jonringer]

For the transition period ( NixOS 21.11), I think keeping the old /run/opengl-driver would help alleviate a lot of the pain, would just like to get the ball rolling away from using opengl explicitly

[nrdxp]

I agree. Also, on a related note, having to specify your graphics driver at the xserver level in the module system feels wrong to me. I'm still not exactly sure how it maps given names to driver packages either.

[jonringer]

I propose two changes:

• move /run/opengl-driver/ -> /run/gpu-driver/
  • make /run/opengl-driver/ a symlink to /run/gpu-driver/ for backwards compatibility of existing derivations
• services.xserver.videoDrivers -> hardware.videoDrivers
  • add a (mkRemovedModule services.xserver.videoDrivers hardware.videoDrivers)

[jonringer]

potential future work as well:

• addOpenGLRunpath -> addGPURunpath
  • Until 21.11 EOL, have it add both /run/opengl-driver/ and /run/gpu-driver/, to avoid system vs package invariance

[jonringer]

I'm also kind of wondering whether gpu-driver is just another fallacy in naming, and we should really be exposing something like, /run/system-driver/ would be even more appropriate, as other hardware-accelerated devices such as tpus, fpga's, and others would also likely need to import "libraries which are determined by the system, and need to be available at runtime".

[nixos-discourse]

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/how-to-run-bevy-game-in-nixos/17486/11