| 22 Feb 2024 |
 raitobezarius | what does already wrapped means | 17:42:25 |
| raitobezarius | because I'd imagine that | 17:42:28 |
| raitobezarius | targets.nixos cfg = cfg // { os = "nixos"; } ? | 17:42:46 |
| raitobezarius | or would you imagine | 17:42:52 |
| raitobezarius | targets.nixos cfg = { _type = "nixos"; module = cfg; ... } ? | 17:43:01 |
| raitobezarius | In reply to @zhaofeng:zhaofeng.li
There would be a registry attrset with definitions for each target type, and the os attribute can either be a string (in which case it will look up the registry) or an explicit target definition OK, how do you see the definition for activation ? | 17:43:13 |
| raitobezarius | right now, you can do colmena apply dry-activate, etc. | 17:43:28 |
| raitobezarius | how would we translate this in the registry configuration module | 17:43:37 |
 Zhaofeng Li | In reply to @raitobezarius:matrix.org
targets.nixos cfg = { _type = "nixos"; module = cfg; ... } ? This, which is closer to ma27 's model | 17:43:42 |
 ma27 | In reply to @zhaofeng:zhaofeng.li
Interesting, the os key sounds like what I have in mind. I assume eval.nix would inject os for the deployment-wide modules to consume? not sure if I have done that already (the current draft is very much oriented on what I needed), but it would be trivial. | 17:43:54 |
| raitobezarius | In reply to @zhaofeng:zhaofeng.li
This, which is closer to ma27 's model yeah so I agree with this | 17:44:06 |
| raitobezarius | I like this one too | 17:44:14 |
| raitobezarius | because low level users can do much more with it | 17:44:19 |
| raitobezarius | so I gather that colmena upstream would be interested in this sort of features | 17:44:35 |
| raitobezarius | so it may make sense just to send PRs towards it (?) | 17:44:41 |
| Zhaofeng Li | In reply to @raitobezarius:matrix.org
OK, how do you see the definition for activation ? I think a good start would be to just have the activation commands, but it could accept a script with a defined interface | 17:46:32 |
| raitobezarius | you mean | 17:46:48 |
| raitobezarius | registry.nixosSystems.activation.dry-activate = "switch-to-configuration dry-activate"; or something like that? | 17:47:06 |
| Zhaofeng Li | Yeah, something like that | 17:47:22 |
| raitobezarius | that makes sense to me | 17:47:38 |
| 23 Feb 2024 |
|  @janejasperous:one.ems.host left the room. | 16:35:34 |
| 25 Feb 2024 |
|  Frédéric Christ joined the room. | 10:21:20 |
|  polygon (she/it) - migrating to @polygon:catgirl.cloud ⚡️ changed their display name from polygon (she/it) ⚡️ to polygon (she/it) - migrating to @polygon:catgirl.cloud ⚡️. | 22:08:53 |
| 26 Feb 2024 |
|  aflox joined the room. | 10:34:58 |
| aflox | Hi everyone 👋
I'm browsing over the colmena documentation coming from nixops and have a question regarding pinning meta.nixpkgs to an initialized attribute set (I'm using flakes) and cross-architecture builds. I'm assuming that simply setting nixpkgs.system on the node is probably not sufficient as the <nixpkgs> set is already initialized, right? What would be the recommended way to handle this ? Have a nodeNixpkgs set for everything that's different from the local system ? | 10:38:51 |
 dantefromhell | In reply to @aflox:matrix.org
Hi everyone 👋
I'm browsing over the colmena documentation coming from nixops and have a question regarding pinning meta.nixpkgs to an initialized attribute set (I'm using flakes) and cross-architecture builds. I'm assuming that simply setting nixpkgs.system on the node is probably not sufficient as the <nixpkgs> set is already initialized, right? What would be the recommended way to handle this ? Have a nodeNixpkgs set for everything that's different from the local system ? I'm cross-compiling aarch64 (for a raspberry) on x86-64. it require binfmt to be setup correctly.
other than that i'm setting nixkpgs.system = "aarch64-linux"; in the host declaration, I dont use nodeNixpkgs.
it builds with colmena build | 14:13:24 |
|  Michael Peyton Jones changed their display name from michaelpj to Michael Peyton Jones. | 16:22:02 |
| 29 Feb 2024 |
|  @wimpress:matrix.org joined the room. | 21:11:05 |
| 2 Mar 2024 |
|  @ktemkin:katesiria.org joined the room. | 08:01:19 |
|  Qyriad joined the room. | 08:09:30 |
