| 24 Jul 2021 |
yusdacra | Hm well at least nix flake show works now | 16:25:50 |
yusdacra | 😅 | 16:25:55 |
David Arnold (blaggacao) | Those damn, module system errors. I hope we get better typing and merging from nickel soonish 🙏 | 16:26:01 |
David Arnold (blaggacao) | * Those damn module system errors. I hope we get better typing and merging from `nickel` soonish 🙏 | 16:26:07 |
David Arnold (blaggacao) | * Those damn module system errors. They are as informative as shit. I hope we get better typing and merging from `nickel` soonish 🙏 | 16:26:28 |
yusdacra | Agreed | 16:27:14 |
yusdacra | https://0x0.st/-WXM.txt | 16:27:45 |
yusdacra | This is the new error trace | 16:27:51 |
@timdeh:matrix.org | Yeah, I'm really keeping 🤞 that the errors will be far simple to debug thanks to the contract constraints. | 16:27:52 |
@timdeh:matrix.org | It looks like the only thing I can see in there from your config is the etc.registry portion, the rest is library traces | 16:29:48 |
@timdeh:matrix.org | * It looks like the only thing I can see in there from your config is the etc."nix/registry.json" portion, the rest is library traces | 16:30:20 |
yusdacra | Hmm | 16:30:23 |
yusdacra | Ah | 16:30:59 |
yusdacra |  Download image.png | 16:31:06 |
yusdacra | it was this | 16:31:10 |
yusdacra | yay, it's building, after fixing some ourLib errors | 16:32:24 |
David Arnold (blaggacao) | bud is a functor. | 16:32:26 |
yusdacra | In reply to @blaggacao:matrix.org
bud is a functor. I see | 16:32:45 |
David Arnold (blaggacao) | 😇 | 16:32:44 |
yusdacra | Thanks for the help | 16:32:55 |
David Arnold (blaggacao) | Haha, I think that breaks a few tacit downstream assumptions 😁 | 16:33:24 |
David Arnold (blaggacao) | nickel 🙏 | 16:33:33 |
@timdeh:matrix.org | I just realized that I should add a module option containing a list of branch names that don't get deleted by quick-nix-registry even if they don't exist upstream. Would be a good way to make your own branches containing PR patches rebased ontop of the latest unstable or release 🤔 | 16:39:41 |
@timdeh:matrix.org | then you could just refer to them in your flake as nixpkgs/my-super-cool-branch | 16:40:10 |
David Arnold (blaggacao) | Inputs Patching Light (TM) | 16:40:34 |
@timdeh:matrix.org | basically yeah 😆 | 16:40:47 |
| 25 Jul 2021 |
fufexan | is there any way in fup to remove a channel? | 17:03:51 |
fufexan | a devshell channel is autogenerated because of legacyPackages | 17:04:10 |
fufexan | should I fetchFromGithub in a separate file then point the revision and sha to flake.lock? | 17:04:38 |
h4rdstyl3z | Hey everyone! I have recently decided to give devos a try and started converting my pre-existing NixOS configuration to its format and I have a couple of doubts that I couldn't solve through the documentation and I'd like to confirm with you:
- Is it possible to remove inputs from the main
flake.nix? Specifically, I'd like to remove nixos-hardware, since I won't use it (as there's nothing relevant there for my use case). Is it just a matter of removing the input itself or is there a more involved process?
- From nxdxp's config I gathered that it's possible to split option declarations throughout different files and it all gets merged (for instance, several
environment.systemPackages declarations in different files), but does this apply everywhere? Are there any special considerations to be had (exceptions, edge cases, etc. that I need to be wary of)?
Thanks in advance for the work put into this project!
| 20:34:18 |