| 25 May 2022 |
 reivilibre | wonder if you need nativeBuildInputs, but that's just an idle thought | 14:00:33 |
| reivilibre | hm I probably have it backwards | 14:01:59 |
 K900 | You probably want to remove the manual cflags and add pkg-config to nativeBuildInputs instead | 14:02:45 |
| reivilibre | I don't know but should you be passing FFTW as a build input in an override for pyfftw rather than your package? | 14:03:35 |
| K900 | Also that yes | 14:04:08 |
| 26 May 2022 |
 Loïc Reynier | Removing the cflags and adding pkg-config as nativeBuildInputs did not make it work | 16:49:25 |
| Loïc Reynier | I thought that the packages passed in buildInputs would be available for all packages built in the environment, so it would not be necessary to add build input for all the packages | 16:51:49 |
 adisbladis | In reply to @loicreynier:matrix.org
I thought that the packages passed in buildInputs would be available for all packages built in the environment, so it would not be necessary to add build input for all the packages No, they will not be passed to the entire graph. You're looking for overrides. | 16:53:21 |
| Loïc Reynier | Thanks you, it did the trick:
overrides = prev.poetry2nix.overrides.withDefaults (self: super: {
pyfftw = super.pyfftw.overrideAttrs (
old: {
buildInputs = with prev; [
fftw
fftwFloat
fftwLongDouble
];
});
| 17:11:29 |
| Loïc Reynier | * Thanks you, it did the trick:
overrides = prev.poetry2nix.overrides.withDefaults (self: super: {
pyfftw = super.pyfftw.overrideAttrs (
old: {
buildInputs = with prev; [
fftw
fftwFloat
fftwLongDouble
];
});
});
| 17:11:59 |
| Loïc Reynier | * Thanks you, it did the trick:
overrides = prev.poetry2nix.overrides.withDefaults (self: super: {
pyfftw = super.pyfftw.overrideAttrs (
old: {
buildInputs = with prev; [
fftw
fftwFloat
fftwLongDouble
];
});
});
| 17:12:09 |
| adisbladis | Add it upstream in https://github.com/nix-community/poetry2nix/pull/649 | 17:14:35 |
|  madhadder joined the room. | 17:58:46 |
|  notgne2 joined the room. | 22:19:08 |
| 3 Jun 2022 |
|  gmacon joined the room. | 19:58:51 |
| 4 Jun 2022 |
|  schuelermine joined the room. | 12:31:16 |
| schuelermine | Hi! I’ve never used Poetry before but I want to package a project that uses it. Can I use the Poetry2Nix functions directly inside Nixpkgs? I noticed that poetry build generates a dist directory and the tarball inside contains a setup.py. Should I specify the Poetry2Nix call as src? I’m unsure how this is supposed to work. | 12:33:29 |
| adisbladis | In reply to @schuelermine:matrix.org
Hi! I’ve never used Poetry before but I want to package a project that uses it. Can I use the Poetry2Nix functions directly inside Nixpkgs? I noticed that poetry build generates a dist directory and the tarball inside contains a setup.py. Should I specify the Poetry2Nix call as src? I’m unsure how this is supposed to work. You don't use the build directory from poetry build for packaging. | 13:23:04 |
| adisbladis | That directory is used for publishing on pypi | 13:23:20 |
| adisbladis | You should just point poetry2nix to the sources | 13:23:31 |
| adisbladis | The setup.py is a compatibility thing | 13:23:45 |
| schuelermine | Oh OK | 13:26:16 |
| schuelermine | Thanks | 13:26:27 |
| adisbladis | Internally poetry still generates the setup.py at build time iirc | 13:26:48 |
| adisbladis | But that's not something you need to bother with, it's an implementation detail | 13:26:59 |
| schuelermine | But is it correct to put fetchFromGitHub or similar in projectDir? | 13:35:37 |
| schuelermine | And is the result from the call to mkPoetryApplication a derivation that can be put into nixpkgs? | 13:35:54 |
| adisbladis | You can do that, but that would result in IFD | 13:36:00 |
| adisbladis | Which isn't allowed in nixpkgs | 13:36:08 |
| schuelermine | Oh | 13:36:14 |
