Skip to content
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

pssh: ensure runtime dependencies are propagated #43820

Closed
wants to merge 1 commit into from

Conversation

Twey
Copy link
Contributor

@Twey Twey commented Jul 19, 2018

Motivation for this change

Makes sure that openssh and rsync are present when running pssh or prsync. These tools give very confusing error messages if they aren't.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Fits CONTRIBUTING.md.

@@ -20,6 +20,8 @@ pythonPackages.buildPythonApplication rec {
done
'';

propagatedBuildDependencies = [ openssh rsync ];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that would be called propagatedBuildInputs - and given these two are already specified explicitly in bin/* after postPatch, they should be automatically added as runtime dependencies:

If the build was successful, Nix scans each output path for references to input paths by looking for the hash parts of the input paths. Since these are potential runtime dependencies, Nix registers them as dependencies of the output paths.

@Twey
Copy link
Contributor Author

Twey commented Jul 20, 2018

I realize this isn't necessary — I was encountering a problem in which prsync wasn't finding rsync, and assumed I needed to make rsync a dependency, but I now realize it was just because I had a -e argument that didn't use an absolute path, so that's my problem. Closing.

@Twey Twey closed this Jul 20, 2018
@flokli
Copy link
Contributor

flokli commented Jul 21, 2018

ok :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants