| 6 Sep 2024 |
 emily | we do package unfree games | 20:27:23 |
| emily | but do we want to get in the business of packaging every game that is only available through Steam? probably no? | 20:27:33 |
| emily | we have a general-purpose fetcher and runner for that packaged called Steam | 20:27:47 |
| emily | not to say that there aren't uses for what you made! | 20:27:54 |
| emily | I think there could be reasons to include it in Nixpkgs. for instance, what if someone wants to write a NixOS module for a proprietary game server only available through Steam? | 20:28:13 |
 aidalgol | Oh yeah, I didn't read it that way at all. | 20:28:24 |
| emily | that would make sense. we have a Minecraft server module. | 20:28:25 |
| emily | and at that point, I would be fine with fetchSteam being in-tree | 20:28:32 |
| emily | but until that point, it doesn't seem worth it | 20:28:46 |
| aidalgol | In reply to @emilazy:matrix.org
I think there could be reasons to include it in Nixpkgs. for instance, what if someone wants to write a NixOS module for a proprietary game server only available through Steam? I've written one, and it's available as a flake: https://github.com/aidalgol/valheim-server-flake/ | 20:28:58 |
 magic_rb | So youre sayibg if i write a arma 3 module, we can merge it, got it 🫡 | 20:29:03 |
| emily | right :) | 20:29:05 |
| emily | so if you wanted to upstream that, go ahead IMO | 20:29:11 |
| aidalgol | I don't think that should go into nixpkgs because of how hacky it has to be. | 20:29:16 |
| emily | ha | 20:29:27 |
| emily | unlike the rest of NixOS :P | 20:29:32 |
| aidalgol | I mean, see the "Notes on using mods" section. | 20:30:29 |
| 7 Sep 2024 |
|  lunik1 changed their profile picture. | 01:45:15 |
 SomeoneSerge (back on matrix) | zowoq btw I tried a bunch of revisions from the hydra history (e.g. https://hydra.nix-community.org/eval/50299#tabs-inputs) and I never get a cache hit with
NIX_PATH=nixpkgs=https://github.com/NixOS/nixpkgs/archive/66a352a3f27a2eb2f27e42a13c6fe245d3be2b98.tar.gz nix build -f '<nixpkgs>' python3Packages.torch
| 19:53:14 |
 zowoq | I get a cache hit from that. | 23:51:24 |
| 8 Sep 2024 |
| SomeoneSerge (back on matrix) | H'm, I'll look into my config again | 01:46:57 |
|  @jquispe:matrix.org removed their display name jquispe. | 15:49:07 |
| @jquispe:matrix.org left the room. | 15:49:13 |
| 10 Sep 2024 |
|  moved to @amadaluzia:tchncs.de changed their display name from (lambda (u) (format nil "~A lost their email!" u)) "Artur Manuel" to Artur Manuel (on break). | 17:32:50 |
| moved to @amadaluzia:tchncs.de changed their profile picture. | 17:35:12 |
| moved to @amadaluzia:tchncs.de changed their display name from Artur Manuel (on break) to (lambda (u) (format nil "~A is not using Matrix right now." u)) "Artur Manuel". | 17:36:48 |
| 11 Sep 2024 |
|  Sr. Estegosaurio joined the room. | 12:49:01 |
 Matt Sturgeon | Do we have a nix-community "bot" account we can use for automated tasks.
Note that it can't be an actual bot (GitHub App), because that won't trigger CI when it pushes. Instead it should be a "machine user" as described here:
User accounts are *intended" for humans, but you can create accounts to automate activity on GitHub. This type of account is called a *machine user". For example, you can create a machine user account to automate continuous integration (CI) workflows.
Managing bots and service accounts with two-factor authentication may also be relevant.
In my case, I just want to nominate a @nix-community-bot as the user that will rebase commits when using Mergify's queue. See this discussion for context.
Therefore it needs to be a regular GitHub user, with write access to nixvim (wider access would be fine, so long as only trusted nix-community admins have access to log in as the user). The user must also have logged in to Mergify's dashboard. | 14:55:47 |
| Matt Sturgeon | * Do we have a nix-community "bot" account we can use for automated tasks?
Note: it can't be an actual bot (GitHub App), because that won't trigger CI when it pushes. Instead it should be a "machine user" as described here:
User accounts are intended for humans, but you can create accounts to automate activity on GitHub. This type of account is called a machine user. For example, you can create a machine user account to automate continuous integration (CI) workflows.
Managing bots and service accounts with two-factor authentication may also be relevant.
In my case, I just want to nominate a @nix-community-bot as the user that will rebase commits when using Mergify's queue. See this discussion for context.
Therefore it needs to be a regular GitHub user, with write access to nixvim (wider access would be fine, so long as only trusted nix-community admins have access to login as the user). The user must also have logged in to Mergify's dashboard.
| 15:32:57 |
| Matt Sturgeon | If not, could we add one? | 17:27:48 |
