| 6 Sep 2021 |
 Roos | In a NixOS configuration you can do something like this: https://gitlab.com/roosemberth/dotfiles/-/blob/master/nix/machines/tests/base.nix#L3 | 14:41:03 |
 TyberiusPrime | which leads to the question how I get the modulePath in this case... all I have is a flake input, whatever that is :) | 14:42:00 |
| TyberiusPrime | (outPath is promising) | 14:42:36 |
| TyberiusPrime | indeed "${nixpkgs.outPath}/pkgs/development/r-modules/generic-builder.nix" get's me a new exciting error message | 14:44:42 |
| Roos | I would try to toString the nixpkgs argument and access the subpath. | 14:45:16 |
| Roos | It's progress \o/ | 14:46:14 |
 ilkecan | toString drv and drv.outPath is the same | 14:51:15 |
|  papojari changed their profile picture. | 21:17:49 |
| papojari changed their profile picture. | 21:18:35 |
| papojari changed their profile picture. | 21:18:52 |
| papojari changed their profile picture. | 21:20:34 |
 colemickens 🏳️🌈 | uh... you can just use it directly.... | 22:50:49 |
| colemickens 🏳️🌈 | import "${inputs.nixpkgs}/nixos/modules/....." whatever just works | 22:51:02 |
| 7 Sep 2021 |
|  Buckley left the room. | 17:08:43 |
| Buckley joined the room. | 17:08:55 |
| Buckley left the room. | 17:10:57 |
| ilkecan | Regarding apps and defaultApp outputs; I was using them to specify the executable name. But after learning about meta.mainProgram, I can't see how they are useful now. Why would I want to create them? | 20:38:47 |
| ilkecan | * Regarding apps and defaultApp outputs; I was using them to specify the executable name. But after learning about meta.mainProgram, I can't see how they are useful now. Why would I want to create them? https://nixos.org/manual/nixpkgs/unstable/#var-meta-mainProgram | 20:42:11 |
| ilkecan | Only reason I can think of is that I have packages.foo and I want to do nix run '.#bar' rather than nix run '.#foo' | 20:44:21 |
| 8 Sep 2021 |
|  mbprtpmnr joined the room. | 13:49:42 |
| 9 Sep 2021 |
| colemickens 🏳️🌈 | I seem to have done it again, I have an environemtn where I supposedly have unstable nix, but supposedly "print-dev-env" isn't a command? | 17:46:16 |
| colemickens 🏳️🌈 | The CLI didn't change again did it? I think there's something else super obvious that I'm missing for some reason | 17:46:30 |
| colemickens 🏳️🌈 | It's from nix-direnv too, somehow it finds an old (Wrong) nix version to use :/ | 17:49:05 |
| colemickens 🏳️🌈 | nix --version says 2.4pre... but when I run direnv allow I get an error from a nix-2.3 build :/ | 17:49:29 |
 tomberek | colemickens 🏳️🌈: are you on home-manager and direnv is using legacy Nix in its PATH? | 17:57:29 |
| colemickens 🏳️🌈 | Well, I'm not on HM, but these instructions are using nix-env | 18:06:57 |
| colemickens 🏳️🌈 | I can just link you, https://github.com/colemickens/nixpkgs-wayland/blob/master/.gitpod.Dockerfile#L27 | 18:07:14 |
| colemickens 🏳️🌈 | I'm just trying to get a flakey-nix-direnv-y gitpod setup going. | 18:07:26 |
| colemickens 🏳️🌈 | Despite these commands, when I fire it up and hit direnv allow I get the behavior I described above (it does sorta look like direnv's using a bundlded nix?) | 18:07:59 |
| colemickens 🏳️🌈 | but not sure what the fix is, I guess. When I skimmed nix-direnv's source, I thought it looked like it ought've been trying to use the newer nix from the nix-profile, but obviously not. | 18:08:30 |
