| 11 Aug 2024 |
 qu4pk4 | My Flake is part of a research into libs/pkgs, so I am ok with it not fitting 100% into the infra. | 20:02:50 |
| qu4pk4 | Nix doesn't seem to be used much for supporting any version of lib, but the strictness and constraints feel like a good match for that use case. | 20:04:32 |
| qu4pk4 | Especially, for research reproduceability. | 20:04:52 |
| qu4pk4 | Another thing: installCheck phase is ran when doInstallCheck is set to true according to https://nixos.org/manual/nixpkgs/stable/#var-stdenv-doInstallCheck, but not when cross-compiling. I can't get my installCheck phase to run in a flake that uses flake-utils. Is the cross-compiling kicking in? | 20:13:20 |
| qu4pk4 | I am building with nix build '#pkg.ver' therefore I am not really thinking I am cross-compiling. | 20:13:48 |
 emily | In reply to @qu4pk4:matrix.org
Is there a good reason, why it doesn't/cannot work? the schema forbids it. legacyPackages lets you put arbitrary data in, which is why Nixpkgs uses it | 20:15:37 |
 tomberek | qu4pk4: Eelco is working on a flake-schemas effort to make supporting various schemas in the the top-level outputs. Regardless, you can place a "lib" wherever you wish. Nixpkgs itself places "lib" output into the top-level of the flake. | 22:29:56 |
| 12 Aug 2024 |
| qu4pk4 | Thanks | 07:44:21 |
| qu4pk4 | How to use passthru.tests for testing Flake package builds? My idea is to build static libraries and tests that the lib<name>.a indeed exists by compiling a simple source. | 07:45:44 |
