| 23 Apr 2024 |
 truh | Does it need to be that strict in fixed output derivations? Private git repos work too. | 09:49:56 |
 @malteneuss:matrix.org | In reply to @matthewcroughan:defenestrate.it
netrc_file is always "" because nixPath is always [] in pure-eval Thanks for the feedback. The Nix flake variant indeed was missing in my PR. I added a few paragraphs how to add env vars to the nix-daemon (i think this is the only working way for flakes). Could you take a look again?
btw, thanks for your awesome talks on Nix for Docker (the main reason my company is willing to try Nix) and for Riscv.
| 19:55:13 |
| @malteneuss:matrix.org | In reply to @truh:matrix.org
Does it need to be that strict in fixed output derivations? Private git repos work too. According to my current understanding the correct way is to not let code inside the sandbox fetch things with credentials (due to security concerns) but let nix do that outside of the sandbox. I think there are some special builtins.fetchers that can take care of that. I may take a look at this once our Python backend services run with poetry2nix and Docker. | 19:59:28 |
 matthewcroughan | In reply to @malteneuss:matrix.org
Thanks for the feedback. The Nix flake variant indeed was missing in my PR. I added a few paragraphs how to add env vars to the nix-daemon (i think this is the only working way for flakes). Could you take a look again?
btw, thanks for your awesome talks on Nix for Docker (the main reason my company is willing to try Nix) and for Riscv.
Thanks! | 21:59:21 |
| matthewcroughan | No, I believe there is no way to pass the NETRC file in, even following your documentation, because poetry2nix has the above bug in it that makes stuff only work via -I which isn't available in pure-eval. | 21:59:48 |
| matthewcroughan | I'm triple checking that here | 21:59:55 |
| matthewcroughan | Yeah, fixed it here anyway https://github.com/nix-community/poetry2nix/pull/1612 | 22:44:03 |
| 25 Apr 2024 |
|  @delroth:delroth.net left the room. | 14:44:15 |
|  cullenmcd joined the room. | 17:41:30 |
| 26 Apr 2024 |
| matthewcroughan | In reply to @k900:0upti.me
Any poetry2nix overrides are applied on top of nixpkgs overrides Is it possible we could go over this again please? I'm really trying to understand it, and would like to understand this code you wrote a bit better https://github.com/nix-community/poetry2nix/blob/master/default.nix#L233-L285 | 13:11:23 |
| matthewcroughan | https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/development/python-modules/apsw/default.nix#L39 | 13:11:36 |
| matthewcroughan | apsw is a derivation that exists in nixpkgs. When poetry2nix encounters apsw in the pyproject.toml, does it use any information from nixpkgs that is already there, or is it making a completely unique derivation that doesn't re-use anything from nixpkgs? | 13:12:07 |
| matthewcroughan | I'm about to submit a fix for apsw in the overrides.nix in poetry2nix, but want to understand it more first | 13:12:26 |
