| 22 Jun 2025 |
Rene | Hello, anyone familiar with nixGL?
| 13:35:13 |
Sandro 🐧 | What is you actually question and is it even flakes related? | 14:15:43 |
Rene | It is. I have an app that is built with a flake. It has a UI, so to run it, I have to do nixGL ./result/bin/myapp.
| 14:17:09 |
Rene | I'm trying to bundle it into a Docker image and I wonder if I can bundle nixGL in the image, or if that defeats the purpose given that nixGL is an impure compat layer to the world outside nix
| 14:18:29 |
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 |