| 1 Feb 2023 |
 K900 | Or a Rust thingy | 08:58:20 |
 Arson Copperflame | The problem is that this is extraInit, so that won't work. Python's got its own problems. I've come to like powershell, but then I had to pass commands (as strings) from powershell to bash (for the tests so pwsh -> docker or wsl -> syschdemd -> bash) and the gates of hell opened before me | 08:59:01 |
| K900 | Haha | 09:00:18 |
| K900 | eval $(${shim}/bin/split-path) goes brr | 09:00:34 |
| K900 | (actually doing that btw) | 09:00:42 |
| K900 | https://github.com/nix-community/NixOS-WSL/pull/214 | 09:18:14 |
| K900 | Actually did that btw | 09:18:17 |
 Sandro 🐧 | Should we ask https://github.com/msteen/nixos-vscode-server to adopt into nixos-wsl? | 09:58:49 |
| Sandro 🐧 | In reply to @nzbr:nzbr.de
While you're at it: command grep should probably be something like ${pkgs.gnugrep}/bin/grep to avoid unfortunate surprises on exotic configs aka mine 😆 | 09:59:03 |
| Sandro 🐧 | In reply to @nzbr:nzbr.de
The problem is that this is extraInit, so that won't work. Python's got its own problems. I've come to like powershell, but then I had to pass commands (as strings) from powershell to bash (for the tests so pwsh -> docker or wsl -> syschdemd -> bash) and the gates of hell opened before me na, no more powershell. I want to be able to fix my things. | 09:59:44 |
| Arson Copperflame | In reply to @sandro:supersandro.de
Should we ask https://github.com/msteen/nixos-vscode-server to adopt into nixos-wsl? I'm running that and it works fine. In theory, we could just import that flake | 10:00:04 |
| Sandro 🐧 | Same, just was thinking if this would make things easier for us | 10:02:07 |
| Sandro 🐧 | I am not sure if we should do the updater in the distro launcher | 10:17:38 |
| Sandro 🐧 | IMO it probably opens a new area of problems | 10:17:56 |
| Arson Copperflame | It's a script at a fixed location inside the tarball (/nix/wsl-installer/updater.sh currently), that the launcher runs. It's possible to run the updater without the launcher and the release notes will describe both options | 10:20:11 |
| Arson Copperflame | 
Download image.png | 10:42:11 |
| Arson Copperflame | The magic 22.11 progress-bar just turned green. Now is your chance to come up with possible release names
(or emergency blockers that should be in the release) | 10:43:03 |
| Arson Copperflame | * The magic 22.11 progress-bar just turned green. Now is your chance to come up with possible release names
(or emergency fixes that should be in the release) | 10:43:19 |
| Sandro 🐧 | Why are we not using a standard path like something in /nix/var/nix/profiles/system/? Then we would not need to link that ourself. | 12:42:19 |
| Sandro 🐧 | I mean the updater in itself is a bad idea. NixOS can be configured in so many different ways especially with flakes that it will break for a good chunk of people and I don't want to accumulate all kinds of workarounds for that. | 12:43:20 |
| K900 | When would the updater be triggered anyway? | 12:44:23 |
| Arson Copperflame | When you run the script or nixos.exe update | 12:44:49 |
| K900 | Maybe we should just make it link to some upgrade guide | 12:44:52 |
| K900 | So it's not required for anything external? | 12:45:04 |
| K900 | Then I'd say just drop it honestly | 12:45:12 |
| K900 | It's way too difficult to get correctly in the general case | 12:45:21 |
| Arson Copperflame | It will obviously never work if you import the module yourself, all it does is replace the files in /etc/nixos/nixos-wsl and offer you to run nixos-rebuild switch(if it doesn't detect that you aren't using /etc/nixos/configuration.nix)
If your config comes from anywhere else, it does absolutely nothing. I don't see a way how you could break your system with it in a way that you couldn't by putting the files there manually | 12:50:13 |
| K900 | Maybe we should just default to generating the system config with flakes or even something like niv | 12:51:43 |
| K900 | So there's an obvious way to update all the inputs | 12:51:51 |
| Arson Copperflame | The idea is that when the MS Store (once we're on there) pushes a new version of the launcher to your device, it prompts you to run nixos update to use the version of our module that comes bundled with the launcher. It will however only do that, if NixOS-WSL-version outputs a version string, which it won't do if the version of the module you are running was pulleys from git | 12:52:45 |
