You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cross-compiled closures are useful for deploying to compact embedded systems, so bringing all this baggage is a show stopper. For reference, a non-cross compiled package has minimal dependencies:
This is a known issue. This requires tracking what packages don't clean up their references. As there are potential a lot (cross-compiling hasn't gotten much attention yet) I don't see much point in keeping an issue open for it so I am closing it (for now).
Are there related issues that you could point me to so I can learn more? Is this a package by package tidy-up or central infrastructure to do this automatically?
Regarding Python I'll be looking at #53320. Aside from that, there have been a couple of people working on the infrastructure. That is now in place, though some improvements are needed, such as patchShebangs #33956.
But regarding the issue you've raised. It's matter of fixing expressions. They've never been written with cross-compilation in mind.
Issue description
A closure for a cross compiled packages includes all the build packages:
Cross-compiled closures are useful for deploying to compact embedded systems, so bringing all this baggage is a show stopper. For reference, a non-cross compiled package has minimal dependencies:
Technical details
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste theresults.
The text was updated successfully, but these errors were encountered: