| 21 Jul 2021 |
 David Arnold (blaggacao) | I can't say much about the concrete reasons of the above error, though. | 21:02:14 |
 fufexan | I feel like I'm either over-complicating something or overlays are that complicated themselves | 21:02:41 |
| fufexan | maybe I shouldn't do what I want using overlays? | 21:02:53 |
| David Arnold (blaggacao) | when you use fup you can pass overlays to the channel's overlaysBuilder | 21:03:55 |
| David Arnold (blaggacao) | Then fup will spit out self.pkgs.<channelname> with the overlays applied. | 21:04:20 |
| fufexan | oh, so that will propagate and I will be able to use prev.wine-tkg for example? | 21:04:53 |
| fufexan | I wouldn't want to export those overlays again, but if this makes things easier I don't mind | 21:05:48 |
| fufexan | thanks! | 21:05:50 |
| David Arnold (blaggacao) | I think self.pkgs is also system scoped so it'd be rather self.pkgs.<system>.<channel> | 21:05:52 |
| David Arnold (blaggacao) | (didn't double check right now) | 21:06:02 |
| fufexan | sounds right | 21:06:15 |
| David Arnold (blaggacao) | you can also use digga 🤣👍️ | 21:06:34 |
| David Arnold (blaggacao) | It tries to make that aspect as simple as it can get: https://digga.divnix.com/api-reference-channels.html#channelsnameoverlays | 21:07:07 |
| fufexan | I will check it out, thanks | 21:11:03 |
| fufexan | oh, I just realized that exportOverlays intelligently figured out those overlays come from an input so it didn't export them again | 21:25:39 |
| fufexan | this is too cool! | 21:25:47 |
| 22 Jul 2021 |
 @gytis-ivaskevicius:matrix.org | did we settled down for on exporters naming? | 08:13:28 |
| @gytis-ivaskevicius:matrix.org | Is fup naming more or less the same as devos? | 08:13:50 |
 @kraftnix:matrix.org | In the new changes to digga/devos, is there still a way to access digga's lib? Previously I had some custom modules which used lib.digga.importers.modules (which is now lib.digga.importModules), but it seems that lib.digga no longer contains any actual digga libs when called from within a module in devos. | 14:49:00 |
| @kraftnix:matrix.org | * In the new changes to digga/devos, is there still a way to access digga's lib? Previously I had some custom modules which used lib.digga.importers.modules (which is now lib.digga.importModules), but it seems that lib.digga no longer contains any actual digga libs when called from within a module in devos. | 14:49:36 |
| @gytis-ivaskevicius:matrix.org | Is there anything I could do with this? https://github.com/NixOS/rfcs/pull/96 | 15:11:51 |
| @gytis-ivaskevicius:matrix.org | Like what are the next steps? | 15:12:11 |
 @timdeh:matrix.org | That's what I was wondering. I fairly certain we have a meeting at some point, but I have no idea when 😅 | 15:13:47 |
| @gytis-ivaskevicius:matrix.org | Who is supposed to schedule it? | 15:23:56 |
| @gytis-ivaskevicius:matrix.org | Author? | 15:23:59 |
| @gytis-ivaskevicius:matrix.org | Leader? | 15:24:02 |
| @timdeh:matrix.org | Unfortunately I don't know yet. This is my first time participating in a Nix RFC. Perhaps David Arnold knows more? | 15:35:47 |
| David Arnold (blaggacao) | In reply to @gytis-ivaskevicius:matrix.org
Is fup naming more or less the same as devos? I aligned naming in the most recent commits. All good. | 15:36:49 |
| David Arnold (blaggacao) | In reply to @kraftnix:matrix.org
In the new changes to digga/devos, is there still a way to access digga's lib? Previously I had some custom modules which used lib.digga.importers.modules (which is now lib.digga.importModules), but it seems that lib.digga no longer contains any actual digga libs when called from within a module in devos. That is correct, digga only exports it's own stuff that we (I) eventually want to document in the library reference. All that was coming from nixpkgs is no longer included | 15:38:16 |
| David Arnold (blaggacao) | In reply to @gytis-ivaskevicius:matrix.org
Author? Yes, if the leader doesn't. | 15:38:38 |
