Conversation
nim65s
left a comment
There was a problem hiding this comment.
diff lgtm, builds fine on linux, and the content of the outputs looks fine, thanks !
I'll start nixpkgs-review on x86_64-linux
I'll start nixpkgs-review on aarch64-darwin. |
|
|
|
No new failure accroding to hydra-check. I think it's safe to go. |
|
About failures in linux :
|
LordGrimmauld
left a comment
There was a problem hiding this comment.
overall looks sane, but why are we removing the enable flags? Maintenance load of all the permutations acting potentially unpredictable? Or is there just no scenario in which having them just enabled hurts?
|
These removed enable* flags are enabled by default and not referenced in nixpkgs. If anyone need manually set some flags off (e.g. some component not avaialble on exotic platforms) , i can add them back. |
|
I need to at least be able to easily disable |
|
I think it's valuable to maintain optionality for dependencies that are truly optional, even if Nixpkgs itself doesn't exercise those combinations. It preserves a lot of information about how the package itself is designed to work and how its build system works. If we drop those options, one must often resort to reading READMEs or build scripts in the source to discover what is actually optional and what is required. |
|
Can you open a new pr to re enable the flag, i will approve for it. |
@qbisi didn't you say you'd add those back yourself if they are required? |
|
Yes, i am waiting for pr or i can add them back myself. |
It's not a hard job. but i think pr opened by @de11n will meet his need most probably. |
|
I will open a PR. |
Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.