| 28 Jul 2021 |
 David Arnold (blaggacao) | I started using my lib like so: self.lib = import ./lib.nix; which has { pkgs, inputs }: and then I do:
{ suites, profiles, hardware, self, pkgs, inputs, ... }:
...
chromiumKioskLauncher = (self.lib { inherit pkgs inputs; }).chromiumKioskLauncher;
| 18:17:19 |
| David Arnold (blaggacao) | self and inputs are as of recently passed as _module.args by default. | 18:17:49 |
| David Arnold (blaggacao) | I kind of prefer to work with more namespaces than just pkgs, since it quickly gets really confusing, indeed. | 18:18:55 |
 @timdeh:matrix.org | TIL about:
https://github.com/xxh/xxh
and I think this could be improved/augmented with the help of nix-shell | 18:32:46 |
| @timdeh:matrix.org | might make a nice profile đ | 18:33:33 |
| @timdeh:matrix.org | So I just built a package for it and nix seems to screw it up âšī¸ | 19:04:20 |
| @timdeh:matrix.org | Perhaps better solution would be:
https://github.com/danrabinowitz/sshrc | 19:16:17 |
| @timdeh:matrix.org | then you could just invoke a nix shell from there đ | 19:16:27 |
 @kraftnix:matrix.org | In reply to @blaggacao:matrix.org
Are we talking about pkgs.lib.our as (eventually) applied to all channels via https://github.com/divnix/devos/blob/8b67cae20a110f296abf91cdba94a3946b1ba647/flake.nix#L89-L96? so in my custom module I changed it to pks.lib.our and now it builds fine, thanks. it had worked previously just using the lib rather than pkgs.lib and had no issues until now.
i also noticed a change in the iso, there is no longer a custom /iso/devos folder, so i looked for the source with fd devos /, however if I run nix develop in it like I would have before with /iso/devos, it pulls down a lot of things from the binaries rather than running straight away like before. is this something on my end? I haven't tried building an iso with bud build vm iso since moving over to it from flk.
| 19:52:27 |
