| 1 Feb 2023 |
 K900 | Maybe we should make it a channel | 13:08:33 |
| K900 | And then the updater will just need to switch the channel URL | 13:08:40 |
 Sandro 🐧 | we just should not push updates through the microsoft store. It takes unnecessarily long and I don't want to depend on MS' update policies and what not | 13:09:37 |
| Sandro 🐧 | it would be a lot easier if we just bootstrap nixos with the store app and then only update it to have an up to date base system | 13:10:04 |
 Arson Copperflame | Wouldn't we need additional infrastructure for that though? Also: We only need to serve one specific commit per release | 13:10:08 |
| K900 | No | 13:10:12 |
| Sandro 🐧 | we can point a channel to a branch | 13:10:21 |
| K900 | We can point nix-channel directly at a github tarball URL | 13:10:21 |
| Arson Copperflame | In reply to @sandro:supersandro.de
we just should not push updates through the microsoft store. It takes unnecessarily long and I don't want to depend on MS' update policies and what not You can still update without the launcher knowing | 13:10:57 |
| Sandro 🐧 | and just putting instructions on the update subcommand is a lot more convenient | 13:11:01 |
| Arson Copperflame | The Launcher could check for updates against the GitHub API instead of relying on its own version number | 13:12:13 |
| Arson Copperflame | And we definitely need to come up with a better mechanism to get the version into the module. Adding a file in CI doesn't feel particularly nice, but I had no better idea, because nix strips the .git directory from the input | 13:13:33 |
| Arson Copperflame | As it github gives us a nice json of all releases here https://api.github.com/repos/nix-community/nixos-wsl/releases | 13:18:41 |
| Arson Copperflame | * Github gives us a nice json of all releases here https://api.github.com/repos/nix-community/nixos-wsl/releases | 13:19:01 |
| Arson Copperflame | * GitHub gives us a nice json of all releases here https://api.github.com/repos/nix-community/nixos-wsl/releases | 13:19:07 |
| Sandro 🐧 | In reply to @nzbr:nzbr.de
And we definitely need to come up with a better mechanism to get the version into the module. Adding a file in CI doesn't feel particularly nice, but I had no better idea, because nix strips the .git directory from the input or we just copy lib.version from nixpkgs | 13:31:07 |
| Sandro 🐧 | and sell it as the module for version X of NixOS | 13:31:15 |
| Arson Copperflame | But if we ever want to release between two versions, we'd have no chance to do that
Does nix give us a timestamp to the commit? | 13:35:30 |
| Sandro 🐧 | In reply to @nzbr:nzbr.de
The Launcher could check for updates against the GitHub API instead of relying on its own version number I really don't want to have the extra work for that in the launcher. | 13:41:47 |
| Sandro 🐧 | In reply to @nzbr:nzbr.de
But if we ever want to release between two versions, we'd have no chance to do that
Does nix give us a timestamp to the commit? then we need a version file or manually tag the archive or push it to a branch from where nix downloads things | 13:42:32 |
| Arson Copperflame | In reply to @sandro:supersandro.de
I really don't want to have the extra work for that in the launcher. that's less complex than what it does right now | 13:44:17 |
| Sandro 🐧 | hmmm, well at least something, I guess | 13:56:37 |
| Arson Copperflame | What I want to happen is basically the following: We publish a release on GitHub. The Launcher knows that through some method. It then checks whether or not the user has that commit or a newer one installed and if not, prompts them to update. nixos update is a convenience function that does that for them, provided they are using the default configuration layout
channels might be a way to achieve this, but I don't really know how they work, because I'm using flakes for everything
| 14:04:15 |
| K900 | We can just do a version compare | 14:05:24 |
| K900 | So e.g. if we have a channel pointing at the 22.11.1 tag, we can just compare the tag to known latest | 14:06:16 |
| K900 | And update if needed | 14:06:25 |
| Sandro 🐧 | channels would work like sudo nix-channel --add https://github.com/SuperSandro2000/nixpkgs/archive/refs/heads/nixos-unstable.tar.gz nixpkg | 14:06:42 |
| Arson Copperflame | In reply to @k900:0upti.me
So e.g. if we have a channel pointing at the 22.11.1 tag, we can just compare the tag to known latest Oh yeah right, we could just parse the version from the channel URL | 14:09:41 |
| K900 | Also if we're doing that, we might want to follow home-manager | 14:11:00 |
| K900 | And have a separate stable branch | 14:11:05 |
