| 22 Jun 2025 |
 Rene | I currently have nixGL installed on my profile, but I see in the docs you can use it as a flake input and overlay it on top of nixpkgs
| 14:19:42 |
| Rene | trying to add nixGL to the image is giving me an error that builtins.currentTime is missing, which seems to point to nixGL being impure
| 14:40:02 |
|  ners joined the room. | 18:55:53 |
| ners | Hello, is there a way to execute an attrset with type = "app" that is exposed through a different output than apps? | 18:56:42 |
| ners | I have an "app" (which is a library output, it would never occur to me to make this an app) that I'd like to run with nix run packages.${system}.foo.someApp, but I get the following error:
error: expected flake output attribute 'packages.x86_64-linux.foo.someApp' to be a derivation or path but found a set: { type = "app"; meta = «thunk»; program = «thunk»; }
| 18:58:25 |
| 23 Jun 2025 |
 nebucatnetzer13 | Redacted or Malformed Event | 07:49:12 |
| nebucatnetzer13 | If you can build it you could run the result? We use this at work result=$(nix build .#devShells.x86_64-linux.default --no-link --print-out-paths) and then you could do $result/bin/foo or maybe even something with $(nix build ...) might work. | 07:49:33 |
| ners | $ nix build .#foo.someApp
error: expected flake output attribute 'packages.x86_64-linux.foo.someApp' to be a derivation or path but found a set: { type = "app"; meta = «thunk»; program = «thunk»; }
| 08:06:51 |
| ners | Ah, I can build .foo.someApp.program! Thanks for the tip. :) | 08:07:43 |
| ners | Surprising that I can build it but not run it. | 08:07:56 |
