| 6 Sep 2024 |
 emily | I guess probably many people use them as remote builders. I don't because I'm paranoid and don't trust them | 08:47:39 |
 Jonas Chevalier | yeah good point. this is the matrix room | 08:47:42 |
| Jonas Chevalier | we should probably ask everybody to join this room | 08:48:04 |
| emily | having another room just for that traffic doesn't seem like a bad idea, but I'm not sure there's sufficient cause for it at present | 08:48:04 |
| emily | usually I just notice my builds are going very slow, check top, and go oh okay let's do it later then | 08:48:18 |
 Gaétan Lepage | Yes, I meant having a dedicated one, because this room also has other uses.
But, indeed, it might be overkilled. | 08:49:26 |
| emily | what would really be nice is something more useful than top so that you can see what's actually getting built and how much CPU it's using, esp. if you're running a bunch of builds and one of them is hogging all the CPU or whatever | 08:51:28 |
| emily | (but also to snoop on what others are up to and how long it's likely to take) | 08:51:36 |
| emily | I tried out nix-top but it didn't seem like it really had the info I wanted (some kind of hierarchical breakdown by nix build job, sorted by CPU) | 08:52:00 |
| Gaétan Lepage | That would be immensely helpful indeed. | 08:52:01 |
| Jonas Chevalier | the nix-daemon could also retain who scheduled the build with a little bit of patching | 08:53:36 |
| Jonas Chevalier | * the nix-daemon could also retain who scheduled the build with a little bit of patching (using SO_PEERCRED) | 08:54:43 |
|  Thom Jordan joined the room. | 18:21:14 |
 aidalgol | I've had a few people ask me about moving https://github.com/nix-community/steam-fetcher into nixpkgs. I'm not sure it really belongs there. Any thoughts on this? | 20:14:44 |
| emily | I don't think we'd want to package arbitrary steam games | 20:17:54 |
 magic_rb | +1 dont think this belongs in nixpkgs, the results can never be cached anyway | 20:19:14 |
| magic_rb | But i will use it for my arma server | 20:19:24 |
 Matt Sturgeon | I'm not personally familiar with steam-fetcher, but just asking generally; would it make sense for nixpkgs to maintain fetchers/builders/writers/etc for things not actually used in nixpkgs, but useful out-of-tree? In this case that'd be steam games, I guess. | 20:20:44 |
| emily | I think potentially sure but the bar would be higher | 20:21:32 |
| emily | and then there's things about this that would put it under that bar (in my judgement) | 20:21:40 |
| magic_rb | Can you elaborate? | 20:22:29 |
| emily | well, like you said it's not that it's not used in Nixpkgs but that it never would be used in Nixpkgs, result is uncachable, might even be violating ToS etc. | 20:23:56 |
| magic_rb | Well yeah thats what were discussing | 20:24:32 |
| emily | In reply to @mattsturg:matrix.org
I'm not personally familiar with steam-fetcher, but just asking generally; would it make sense for nixpkgs to maintain fetchers/builders/writers/etc for things not actually used in nixpkgs, but useful out-of-tree? In this case that'd be steam games, I guess. I mean I'm just replying to this | 20:24:47 |
| emily | I think it can make sense in theory but that it doesn't make sense in practice for this | 20:24:56 |
| magic_rb | Yeah i didnt quite get it | 20:25:00 |
| magic_rb | But anyway, i agree with ya | 20:25:14 |
| aidalgol | Anything you would want to use steam-fetcher for would be unfree, because anything FOSS available through Steam will be available via simpler means. | 20:25:52 |
| emily | yeah | 20:27:19 |
| emily | and I mean | 20:27:20 |
