| 11 Jul 2024 |
 Mindavi | I've one question and then I'd say it's good to go, but my bash isn't that great | 07:39:58 |
| 15 Jul 2024 |
|  @sielicki:matrix.org left the room. | 00:28:04 |
|  dminca changed their display name from dminca to nixpkgs. | 17:28:44 |
| dminca changed their display name from nixpkgs to dminca. | 17:42:24 |
| 23 Jul 2024 |
|  Ezzobir Bezziou joined the room. | 08:21:01 |
| 24 Jul 2024 |
|  Redstone changed their display name from redstone-menace to Redstone. | 10:15:29 |
| 26 Jul 2024 |
|  Tristan Ross joined the room. | 03:12:38 |
| 30 Jul 2024 |
| Tristan Ross | Looking into getting Zig to be able to bootstrap Nix. I have started figuring things out. | 04:02:04 |
| Tristan Ross | The idea is to be able to use Zig to bootstrap Nix for LLVM. | 04:02:48 |
 reno | what is the benefit of using zig than just using llvm to bootstrap itself like what is done in freebsd and darwin? | 04:27:39 |
| reno | * what is the benefit of using zig than just using llvm to bootstrap itself like what is done in freebsd and darwin? or gcc like is done on linux | 04:29:13 |
| Tristan Ross | In reply to @paparodeo:matrix.org
what is the benefit of using zig than just using llvm to bootstrap itself like what is done in freebsd and darwin? or gcc like is done on linux Zig prebuilds are a static binary with Clang statically linked in so more of convenience | 04:45:34 |
| Tristan Ross | Also, a bootstrap archive wouldn't be necessary. | 04:46:19 |
| Tristan Ross | Literally just fetchTarball and then use it by using zig cc. | 04:46:40 |
| Tristan Ross | Nixpkgs already has Zig stdenv merged in so some of the existing stuff exists. | 04:47:02 |
 trofi | Redacted or Malformed Event | 05:17:00 |
 Philip Taron (UTC-8) | stdenv folks: https://github.com/NixOS/nixpkgs/pull/330830 is ready for merge, I think. please take a look. | 18:21:47 |
| Philip Taron (UTC-8) | I'm ideating about a fix for https://github.com/NixOS/nixpkgs/issues/328229 that still allows passive viewing but doesn't create such a spew. | 18:57:15 |
| 31 Jul 2024 |
| Philip Taron (UTC-8) | In reply to @philiptaron:matrix.org
I'm ideating about a fix for https://github.com/NixOS/nixpkgs/issues/328229 that still allows passive viewing but doesn't create such a spew. The results of this ideation are here: https://github.com/NixOS/nixpkgs/pull/331383 | 21:52:52 |
 raitobezarius | Not so sure about the package manager changes | 21:54:08 |
| Philip Taron (UTC-8) | I'm super open to what better would look like. | 21:57:56 |
| raitobezarius | I think the nixLogDebug thing is a good idea but I'd generalize it to nixLog $loglevel $msg | 21:58:51 |
| raitobezarius | Have an alias for nixLogDebug | 21:59:02 |
| raitobezarius | Then I'd move setting the env var in the sandbox inside the package manager impl | 21:59:20 |
| raitobezarius | Possibly also the whole design of Nix LOG FD is wrong-ish | 21:59:37 |
| Philip Taron (UTC-8) | In reply to @raitobezarius:matrix.org
Then I'd move setting the env var in the sandbox inside the package manager impl Say more on this? | 21:59:58 |
| raitobezarius | I wouldn't hack in the nixpkgs packaging of the package managers | 22:00:38 |
| raitobezarius | The details are vague to me as well but I think a post patch approach seems wrong to me, it has to be minimally a patch, a proper solution to upstream with a proper PR number / issue which describes what are we trying to solve as a usecase and who uses it in practice and how | 22:01:43 |
| raitobezarius | Like maybe the hack is to have a FD per loglevel and have the stdenv always write all of them, etc. | 22:03:43 |
| raitobezarius | (and let the user choose a dynamic nix3-log level or a global setting) | 22:04:24 |
