-
-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python needs splicing #104135
Comments
I think this is the code you're talking about in the Haskell stuff: nixpkgs/pkgs/development/haskell-modules/make-package-set.nix Lines 99 to 114 in 9a38c3a
Is there some documentation around this? I feel like I am missing the larger picture around this, including what sort of derivations should actually make use of this functionality, how it is implemented under the hood, and what the relationship is to things like The only documentation I've found is a comment in splice.nix, but it doesn't really give a lot to go on: nixpkgs/pkgs/top-level/splice.nix Lines 1 to 23 in 9a38c3a
|
Describe the bug
Non-
buildInputs
that are python packages shouldn't be provided by the same package set in cross builds.(Grep
__splicedPackages
so see the nasty stuff the Haskell and xorg package sets do today, that's what we need to cargo cult.)I'm happy to help fix this, but it would be nice to do in conjunction with the python maintainers rather than pure async.
To Reproduce
On staging today fad48e3:
Expected behavior
those two derivations are the same
Additional context
Notify maintainers
CC @FRidh
Maintainer information:
The text was updated successfully, but these errors were encountered: