Guibou

Haa, damned, indeed, that's a regression introduced by #79 that I merged too quickly. Thank you for the report. You can try previous commit as a workaround.

You can workaround it with: ``` nix-build ./default.nix -A nixGLIntel --arg enable32bits false ```

Ha, @nothingnesses, that's an interesting use case. You see the `{}` in `import (fetchGit {...}) {HERE}`, this is where you put this kind of options. So you should use: ```...

@nothingnesses Works for me in this context: ``` λ walrus ~ → which alacritty alacritty not found λ walrus ~ → nix-shell foo.nix warning: unknown setting 'experimental-features' hint: Using 'master'...

Well, I can push the derivation in `nixpkgs`, but you'll still have to call it manually to setup the desired driver. I'll see if I can find something smart today,...

Actually it may be interesting if I provide a way to easilly wrap another program. So for example, a custom `.config/nixpkgs/nix.conf` would contain something such as: ``` myNixGLNvidia = pkgs.nixGL...

Sorry for the delay. As a workaround, you can always do: ``` nixGL = fetchTarball "https://github.com/guibou/nixGL/archive/master.tar.gz" myNixGL = (import "${nixGL}/default.nix") { nvidiaVersion = "..."; nvidiaHash = "..."; pkgs = pkgs;...

@jsmaniac Thank you for your feedback. > hardcode the list of Nvidia driver versions Yes, definitly yes. This will improves bulid time, reproducibility and everything. The issue is that we,...

> I didn't see where this happens in the code, could you give me a pointer to the relevant code or some comment? I think I slightly misunderstood something in...

@jsmaniac Yes, you got it right. The use case I'm having everyday at work is that I'm working on NixOS but I have different nixpkgs pinned for my clients. So...