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

droopy: init at 20160830 #22499

Merged
merged 1 commit into from
Feb 11, 2017
Merged

droopy: init at 20160830 #22499

merged 1 commit into from
Feb 11, 2017

Conversation

Profpatsch
Copy link
Member

@Profpatsch Profpatsch commented Feb 6, 2017

  • NixOS
  • Tested execution of all binary files (usually in ./result/bin/)


phases = [ "unpackPhase" "installPhase" "fixupPhase" ];

installPhase = ''
Copy link
Member

@aszlig aszlig Feb 10, 2017

Choose a reason for hiding this comment

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

What about just:

install -vD -m 0644 man/droopy.1 "$out/share/man/man1/droopy.1"
install -vD droopy "$out/bin/droopy"

It's much more concise and also doesn't copy files to the wrong directories (like the wrong dir for the manpage) and cause artifacts (like "$out/droopy").


with lib;

buildPythonApplication rec {
Copy link
Member

@aszlig aszlig Feb 10, 2017

Choose a reason for hiding this comment

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

stdenv.mkDerivation with wrapPython in nativeBuildInputs should be enough here as the package doesn't have a setup.py and it also doesn't have any dependencies other than the Python standard library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: enhancement Add something new 8.has: package (new) This PR adds a new package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants