| 7 Apr 2025 |
 John Ericson | https://gist.github.com/Ericson2314/147281788b3b31cfbd4925dc49e3d59b | 15:15:00 |
| John Ericson | btw | 15:15:02 |
| John Ericson | for fixing headers downstream | 15:15:07 |
| John Ericson | tomberek: Mic92 was wondering about setting up the nix-community build bot for hydra for PRs | 15:34:43 |
| John Ericson | (hehe kinda ironic) | 15:34:49 |
| John Ericson | but this would require changing the nixos org settings | 15:34:55 |
| John Ericson | which I think you have the perms to do? | 15:35:03 |
 Mic92 | we first need to make the github app public in nix-community | 15:36:32 |
| 8 Apr 2025 |
|  @ser:sergevictor.eu joined the room. | 10:15:16 |
|  @yuri:peori.space left the room. | 11:23:13 |
 Las | What parts do I need to look at to fully understand the hash modulo stuff? | 12:09:34 |
 Robert Hensing (roberth) | Definitely https://nix.dev/manual/nix/2.28/store/derivation/ and its sub-pages (see the menu, rendered as 4.4.*), as for code, maybe John Ericson has a hint? | 12:15:17 |
| Las |
But rather than somehow scanning all the other fields for inputs, Nix requires that all inputs be explicitly collected in the inputs field. It is instead the responsibility of the creator of a derivation (e.g. the evaluator) to ensure that every store object referenced in another field (e.g. referenced by store path) is included in this inputs field.
Isn't this not true Robert Hensing (roberth) ?
| 12:18:05 |
| Las | If I cat a .drv file it doesn't have explicit inputs | 12:18:27 |
| Robert Hensing (roberth) | Yeah, the fields aren't named, but one of those , separated parts is specifically for declaring inputs using DerivingPaths | 12:19:24 |
| Las | Say I want to output a CA derivation, something like echo hello > /1rz4g4znpzjwh1xymhjpm42vipw92pr73vdgl6xs1hycac8kf2n9,
to be used in a downstream dynamic derivation.
I don't think this is possible if the placeholder path is also /1rz4g4znpzjwh1xymhjpm42vipw92pr73vdgl6xs1hycac8kf2n9 for the derivation
producing the derivation, which seems to be plausible since it seems to be determined by the output name only from testing? | 12:30:10 |
| Las | I really think there needs to be a way to avoid using placeholder paths entirely. They're a code smell. | 12:30:36 |
| Las | The output path should always be at /outputs/<output name> IMO, even if placeholder paths are needed for self-references. | 12:31:28 |
| Las | or is the placeholder path not supposed to depend only on the output name, and I'm testing it wrong somehow? | 12:33:51 |
| @ser:sergevictor.eu left the room. | 13:22:49 |
 @leona:leona.is | It's uncool that https://github.com/NixOS/nixpkgs/issues/393359#issuecomment-2766317573 was just merged as additionally you said that you want to make 2.27 the new default and also that 2.28 has API breakages | 21:15:26 |
| @leona:leona.is | * It's uncool that https://github.com/NixOS/nixpkgs/issues/393359#issuecomment-2766317573 was just merged as additionally you said that you want to make 2.27 the new default for NixOS 25.05 and also that 2.28 has API breakages | 21:15:41 |
