postgresql.pg_config: make overrideable#426704
Conversation
d7082d8 to
a7ff1c9
Compare
|
|
|
|
Looks reasonable on a first glance, but would like to take a closer look. May take a few days, too much other stuff on my plate. |
This allows `postgresql.withPackages` to easily override the paths to the default and man outputs for `pg_config`. It avoids all `buildEnv`-dev-output hackery, which it didn't properly support, and separates the logic cleanly.
This reverts commit 39767f9.
…sable checkPhase" This reverts commit 6dee2b6.
a7ff1c9 to
267991c
Compare
|
Rebased after the nixfmt-bump merge conflict. I would like to proceed with this, because all pg extension's passthru tests are still broken without it. @Ma27 did you have a chance to look at it a bit more? |
|
Sorry, no. Will do my best to do that either today or in the upcoming days! |
Ma27
left a comment
There was a problem hiding this comment.
I'm happy that the messing with multi-out buildEnv can go, thanks! 🎉
This reverts commit ae730b3. The underlying issue was properly fixed in NixOS#426704. The commit this reverts was a temporary workaround.
This allows
postgresql.withPackagesto easily override the paths to the default and man outputs forpg_config. It avoids allbuildEnv-dev-output hackery, which it didn't properly support, and separates the logic cleanly.Closes #425384, reverts #426048.
Things done
nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.