| 27 Jan 2024 |
 @9hp71n:matrix.org | Isn't this "${config.wayland.windowManager.sway.package} some HM thing that should not be used on NixOS ? | 17:52:29 |
| @9hp71n:matrix.org | * Isn't this "${config.wayland.windowManager.sway.package} some HM thing that should not be used on NixOS ?
This one: programs.sway.enable = true; uses other package with some NixOS specific overrides inside. | 17:53:17 |
 x10an14 | In reply to @9hp71n:matrix.org
Isn't this "${config.wayland.windowManager.sway.package} some HM thing that should not be used on NixOS ?
This one: programs.sway.enable = true; uses other package with some NixOS specific overrides inside. Please do document/provide source =) Could be! | 17:53:33 |
| @9hp71n:matrix.org | * Isn't this "${config.wayland.windowManager.sway.package} some HM thing that should not be used on NixOS ?
This one: programs.sway.enable = true; uses other package with some NixOS specific overrides inside.
If it's a NixOS one. | 17:53:52 |
| x10an14 | Bit of a shame if it's the case, 'cause I wanted my HM config to be NixOS independent. But some more coding should provide a way to fix that I suppose. | 17:54:48 |
| @9hp71n:matrix.org | Nevermind, I think it should be okay ?
https://nix-community.github.io/home-manager/options.xhtml#opt-wayland.windowManager.sway.package
Sway package to use. Will override the options ‘wrapperFeatures’, ‘extraSessionCommands’, and ‘extraOptions’. Set to null to not add any Sway package to your path. This should be done if you want to use the NixOS Sway module to install Sway.
I know NixOS module does some things inside:
https://github.com/NixOS/nixpkgs/blob/a77ab169a83a4175169d78684ddd2e54486ac651/nixos/modules/programs/wayland/sway.nix#L34
but they are probably not related your issue.
| 17:57:22 |
| @9hp71n:matrix.org | * Nevermind, I think it should be okay ?
https://nix-community.github.io/home-manager/options.xhtml#opt-wayland.windowManager.sway.package
Sway package to use. Will override the options ‘wrapperFeatures’, ‘extraSessionCommands’, and ‘extraOptions’. Set to null to not add any Sway package to your path. This should be done if you want to use the NixOS Sway module to install Sway.
I know NixOS module does some things inside:
https://github.com/NixOS/nixpkgs/blob/a77ab169a83a4175169d78684ddd2e54486ac651/nixos/modules/programs/wayland/sway.nix#L34
but they are probably not related your issue.
| 17:57:38 |
| @9hp71n:matrix.org | Actually you were running sway from HM, so if you didn't have home-manager.inputs.nixpkgs.follows = "nixpkgs"; (and maybe useGlobalPkgs=true;) it could have different version. | 18:08:27 |
| @9hp71n:matrix.org | * Actually you were running sway from HM, so if you didn't have home-manager.inputs.nixpkgs.follows = "nixpkgs"; (and maybe useGlobalPkgs = true; ?) it could have different version. | 18:09:24 |
| @9hp71n:matrix.org | * Actually you were running sway from HM, so if you didn't have:
home-manager.inputs.nixpkgs.follows = "nixpkgs";
(and maybe useGlobalPkgs = true; ?)
it could have different version. | 18:10:18 |
 K900 | In reply to@9hp71n:matrix.org
Actually you were running sway from HM, so if you didn't have:
home-manager.inputs.nixpkgs.follows = "nixpkgs";
(and maybe useGlobalPkgs = true; ?)
it could have different version. They're doing HM standalone on NixOS | 18:16:24 |
| K900 | So no useGlobalPkgs or follows will help, technically | 18:16:31 |
| @9hp71n:matrix.org | Not sure about useGlobalPkgs.
But even for standalone if they don't do follows wouldn't their sway and all its dependencies be from nixpkgs that is currently locked in HM repo ? | 18:27:16 |
| K900 | Well yes but even if they do it won't help | 18:27:30 |
| K900 | Because they may have different versions of nixpkgs at different times | 18:27:42 |
| K900 | As in, the active nixos may be built from another flake revision | 18:27:57 |
| x10an14 | In reply to @9hp71n:matrix.org
Not sure about useGlobalPkgs.
But even for standalone if they don't do follows wouldn't their sway and all its dependencies be from nixpkgs that is currently locked in HM repo ? I am doing nixpkgs follow on HM flake input | 18:49:20 |
| x10an14 | In reply to @k900:0upti.me
As in, the active nixos may be built from another flake revision This is true. I should get around to unifying. I'm just really enamored with the idea of having a HM config across all my machines (which might not all be NixOS) 100% independent from NixOS itself. | 18:50:12 |
| 28 Jan 2024 |
| K900 | In reply to@x10an14:matrix.org
This is true. I should get around to unifying. I'm just really enamored with the idea of having a HM config across all my machines (which might not all be NixOS) 100% independent from NixOS itself. I completely forgot that I wanted to write this | 11:04:09 |
| K900 | But you can still kinda do that | 11:04:15 |
| K900 | If you have a HM config as a module | 11:04:20 |
| K900 | You can import it standalone or into a NixOS config | 11:04:27 |
| x10an14 | I'm vaguely aware of this, but I haven't deep dived into leveraging nixos's HM module, or "connecting them" as to separately instantiated configurations (and if so, which of the myriad(?) of alternative ways). But thank you for ensuring I'm aware =) | 11:09:09 |
| K900 | Finally | 15:03:15 |
| K900 | All the yuzus are working again | 15:03:20 |
| K900 | https://github.com/NixOS/nixpkgs/pull/283822 | 16:30:10 |
| K900 | Please test the yuzus | 16:30:13 |
| 29 Jan 2024 |
|  Sam Lehman joined the room. | 10:58:36 |
| Sam Lehman set a profile picture. | 11:06:03 |
|  @not-leader:envs.net changed their display name from Not_Leader to not_leader. | 13:00:30 |
