rustPlatform.cargoBuildHook: do not use when buildPhase is set#114669
rustPlatform.cargoBuildHook: do not use when buildPhase is set#114669danieldk wants to merge 1 commit intoNixOS:stagingfrom
Conversation
|
Would it be appropriate to land this on master instead of staging, since it fixes a channel blocker? There are 9 packages that use |
|
@collares I think this change make sense, but I think we're agreed on that packages like |
|
i.e I can just deliver those smaller fixes to master, and this can go through staging. But if @danieldk disagrees with what I just said than I would reconsider. |
|
@worldofpeace That's even better! I just suggested landing this on master because it would reduce the urgency of fixing it the "proper" way for all affected packages, but if you were already planning to fix the channel-blocking ones quickly then it's definitely the best approach. Thanks a lot! Since I guess most packages won't be channel-blocking, here's a list of maintainers of affected packages (excluding
If you were tagged above, you were using |
I fully agree. Merging this results in a lot of rebuilds. |
The new cargoSetupHook makes it easier to work with mixed projects. In this case meson & ninja + rust. See NixOS#114669 (comment)
No, because then everyone would need to rebuild all rust and python packages for the next half day or day. |
|
I think this is superceded by #114716 |
Yep, that's a superset. Closing this. |
Motivation for this change
See #114659.
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)