-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
luarocks-bootstrap: cmake and zip should be propagatedNativeBuildInputs #359822
base: staging
Are you sure you want to change the base?
Conversation
Probably should go into staging... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. But yeah, maybe to staging
I dont quite get the difference propagatedNativeBuildInputs wont be automatically propagated but I amgined the native in EDIT: and yeah staging |
@teto the issue just now is that cmake is build for arm64 when cross compiling from an x86 machine. But I am also wondering why does this need to be a propagating build input? If a build system is required for an ecosystem than either a builder or a build hook should be used. Propagating pulls in cmake in places where they are not required. This is different from python libraries. |
Looking at the ecosystem, I don't see many ruby plugins that would justify having ruby enabled by default.
@@ -16,7 +16,7 @@ luarocks_bootstrap.overrideAttrs (old: { | |||
hash = "sha256-hsjv+jlLsoIDM4gB/0mFeoVu1YZ1I9ELDALLTEnlCF0="; | |||
}; | |||
|
|||
propagatedBuildInputs = old.propagatedBuildInputs ++ [ | |||
propagatedNativeBuildInputs = old.propagatedNativeBuildInputs ++ [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: are you sure file
and nurl
should be propagatedNativeBuildInputs
too?
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.