| 26 Oct 2023 |
 K900 | Yeah | 14:20:24 |
| K900 | Those are also IFD | 14:20:26 |
| K900 | But also, now that we're about to not be in nixpkgs anymore, maybe we should just give up | 14:20:38 |
| K900 | And allow IFD by default | 14:20:42 |
| K900 | It will solve most of the Cargo.lock issues and it will also solve most of the buildsystem overrides because we can just look at the pyproject.toml | 14:21:00 |
 cpcloud | Being able to look at build systems would be realllllly nice | 14:22:25 |
 schmittlauch (he/him) | Hm, removing legacyPackages.poetry2nix from the flake in the latest update broke my setup after re-locking. Not too bad to fix, but unexpected. I guess I ended up with that legacyPackages reference in the first place due to starting with a generic python template that took poetry2nix` from the nixpkgs input, and then transitioned to using the poetry2nix flake. | 21:08:44 |
| schmittlauch (he/him) | For reproducing https://github.com/nix-community/poetry2nix/issues/1351 with the latest master HEAD, I am struggling a bit to rework my flake to use poetry2nix. How do I now get the poetry2nix builders like mkPoetryEnv? | 21:21:35 |
| schmittlauch (he/him) | The template uses
let
# see https://github.com/nix-community/poetry2nix/tree/master#api for more functions and examples.
pkgs = nixpkgs.legacyPackages.${system};
inherit (import poetry2nix { inherit pkgs; }) mkPoetryApplication;
but I do not fully understand how this works in the background. Does this utilise the overlay output of the poetry2nix flake? | 21:23:00 |
| K900 | import poetry2nix { inherit pkgs; } | 21:23:06 |
| K900 | No | 21:23:14 |
| K900 | It just creates an instance of poetry2nix that's not overlayed anywhere | 21:23:34 |
| K900 | It's standalone | 21:23:36 |
| schmittlauch (he/him) | Is poetry2nix specified as an output of that flake? | 21:23:59 |
| schmittlauch (he/him) | Or how is it exposed as a name/ attr? | 21:24:16 |
| K900 | No, poetry2nix is the flake input | 21:24:19 |
| K900 | So it'll resolve to the path of the poetry2nix repo | 21:24:27 |
| K900 | And it will import its default.nix | 21:24:54 |
| K900 | Which is defined like this: https://github.com/nix-community/poetry2nix/blob/master/default.nix | 21:24:57 |
| schmittlauch (he/him) | Yes, but when reading through the actual poetry2nix flake.nix file in the repo I do not understand what actually is imported there. | 21:25:15 |
| K900 | default.nix is what is imported | 21:25:55 |
| schmittlauch (he/him) | Oh well, is this a crude workaround or an actual intended way of using this? | 21:26:13 |
| K900 | We might export it as a function in the flake eventually | 21:26:40 |
| K900 | Similar to say nixpkgs.lib.nixosSystem | 21:26:46 |
| schmittlauch (he/him) | I thought the main idea is that you only reference explicit outputs of other flakes | 21:26:50 |
| K900 | But it is a perfectly fine way to use this | 21:26:53 |
| schmittlauch (he/him) | Okay. thx. | 21:27:10 |
| K900 | And it's better than the old way because it avoids yet another nixpkgs instance | 21:27:15 |
| * schmittlauch (he/him) is still a bit weirded out but starts to understand | 21:27:35 |
| schmittlauch (he/him) | In reply to @k900:0upti.me
And it's better than the old way because it avoids yet another nixpkgs instance Ah, that new instance only happens when using it as an overlay? I saw we now hardcode a list of permittedInsecurePackages. | 21:28:19 |
