| 5 Feb 2023 |
Winter (she/her) | * Agreed -- maybe write that in the comments, so they can see? | 19:06:03 |
@blaggacao:matrix.org | For what it's worth now or later, I packages frappe/bench so interested parties could start playing around with gameplan, should they wish to. | 19:21:51 |
@blaggacao:matrix.org | Thanks to ChatGPT for Nixpkgs this was super easy. 😃 | 19:22:32 |
@blaggacao:matrix.org | * For what it's worth now or later, I packaged frappe/bench so interested parties could start playing around with gameplan, should they wish to. | 19:23:11 |
@blaggacao:matrix.org | In fact, in the spirit of RFC 140, the hardest part was to find the right folder (and some version overrides, to be honest). | 19:27:06 |
@blaggacao:matrix.org | It just got harder and became an evangelization issue after playing a little with it. But that's borderline off topic, here, anyways. | 23:42:32 |
| 6 Feb 2023 |
Gytis Ivaskevicius | Hey guys, not sure what you guys are up to these days but I'd appreciate if you guys could follow up on this blueprints idea, maybe making it a standard in nix ecosystem https://github.com/NixOS/nixpkgs/pull/208020#issuecomment-1419168718 | 14:29:54 |
figsoda | In reply to @gytis-ivaskevicius:matrix.org Hey guys, not sure what you guys are up to these days but I'd appreciate if you guys could follow up on this blueprints idea, maybe making it a standard in nix ecosystem https://github.com/NixOS/nixpkgs/pull/208020#issuecomment-1419168718 The blueprints still looks very nixpkgs-esque to me
I believe that we should not encourage people to depend on nixpkgs and this should be resolved in nix itself.
I can see a callPackage like pattern being lifted to the nix level (maybe in a separate repository core, kind of like nixpkgs.lib), but things like stdenv are strictly nixpkgs, it breaking change in nixpkgs will cause this flake to break, and I'm not seeing anything that refers to nixpkgs in the flake outputs.
about the issue, I like the perSystem pattern that flake-parts uses, maybe this can be supported in a more official way (something in nixpkgs like nixosSystem, or even ootb flakes support)
| 14:56:25 |
figsoda | In reply to @gytis-ivaskevicius:matrix.org Hey guys, not sure what you guys are up to these days but I'd appreciate if you guys could follow up on this blueprints idea, maybe making it a standard in nix ecosystem https://github.com/NixOS/nixpkgs/pull/208020#issuecomment-1419168718 * The blueprints still looks very nixpkgs-esque to me
I believe that we should not encourage people to depend on nixpkgs and this should be resolved in nix itself.
I can see a callPackage like pattern being lifted to the nix level (maybe in a separate repository core, kind of like nixpkgs.lib), but things like stdenv are strictly nixpkgs, it having a breaking change in nixpkgs will cause this flake to break, and I'm not seeing anything that refers to nixpkgs in the flake outputs.
about the issue, I like the perSystem pattern that flake-parts uses, maybe this can be supported in a more official way (something in nixpkgs like nixosSystem, or even ootb flakes support)
| 14:59:45 |
figsoda | * The blueprints still looks very nixpkgs-esque to me
I believe that we should not encourage people to depend on nixpkgs and this should be resolved in nix itself.
I can see a callPackage like pattern being lifted to the nix level (maybe in a separate repository core, kind of like nixpkgs.lib), but things like stdenv are strictly nixpkgs, it having a breaking change in nixpkgs will cause this flake to break, and I'm not seeing anything that refers to nixpkgs in the flake outputs.
about the issue, I like the perSystem pattern that flake-parts uses, maybe this can be supported in a more official way (something in nixpkgs like nixosSystem, or even ootb support in nix)
| 15:02:43 |