| 16 Feb 2024 |
 raitobezarius | i was so close with my .config/nix/ idea | 14:19:51 |
| raitobezarius | just I don't do this sort of shit | 14:19:57 |
 hexa | killing aliases is good shit | 14:20:05 |
| hexa | but what alias am I using? | 14:20:12 |
| raitobezarius | legacy system | 14:20:28 |
| raitobezarius | instead of localSystem or crossSystem I'd assume | 14:20:38 |
| raitobezarius | at this point, this looks like kinda a bug in colmena | 14:20:52 |
| raitobezarius | maybe half half colmena nixpkgs | 14:20:59 |
| hexa | huh, could be | 14:21:01 |
| raitobezarius | but why would it break randomly | 14:21:05 |
| hexa | and like that 😄 | 14:21:12 |
| hexa | fails with localSystem = system the same 🙂 | 14:21:47 |
| raitobezarius | at this point, you want to confirm one thing | 14:24:17 |
| raitobezarius | can you evaluate your system toplevel without colmena? | 14:24:23 |
| raitobezarius | as long as you are not using colmena specific nixos modules, you can just do pkgs.nixos [ (import ./machines/configuration.nix) ] | 14:24:58 |
| hexa | deployment.keys | 14:26:48 |
| hexa | agenix soon-ish | 14:26:59 |
| raitobezarius | you can inject colmena specific modules too in that list | 14:28:00 |
| raitobezarius | and that will fix the thing | 14:28:03 |
| raitobezarius | here's an example on how I do it with flake: | 14:28:08 |
| raitobezarius | https://git.newtype.fr/newtype/newtype-org-configurations/src/branch/main/configurations.nix#L19-L21 | 14:28:38 |
| 20 Feb 2024 |
|  @sofo:matrix.org changed their display name from Sofi to Sofie. | 07:39:10 |
| @sofo:matrix.org changed their profile picture. | 14:39:01 |
| @sofo:matrix.org changed their profile picture. | 14:41:30 |
| @sofo:matrix.org changed their profile picture. | 14:42:42 |
| @sofo:matrix.org changed their profile picture. | 14:44:01 |
| 22 Feb 2024 |
| raitobezarius | Zhaofeng Li: I'm planning to perform a big change in my fork of colmena, i.e. to introduce ways to configure flavors of systems, e.g. NixOS systems, Liminix systems, etc.
My intuition is that all that colmena really care about is NixOS-style mechanisms to copy closures to target system (if needed) and activate the new configuration, with that in mind, I am planning to introduce configuration attribute sets to influence how eval.nix works and which modules does it pass, which activation script will it use and introduce things like nixosConfigurations, liminixConfigurations in the top-level of the hive.
I am aware this is an intrusive change so I was planning to do it in my own fork of colmena and make a new tool out of this which will not be named colmena, I wanted to check with you if you were not interested into the idea (and if it could not make upstream). WDYT?
| 16:35:36 |
| raitobezarius | (To be precise, I'm adding support for Liminix systems and a certain framework to manipulate NETCONF-based appliances) | 16:36:06 |
 Zhaofeng Li | I'm actually interested in a deploy-rs-style "profile" system where the evaluator and deployer are pluggable | 16:37:40 |
| Zhaofeng Li | My main usecase would be to deploy nix-darwin | 16:38:11 |
