-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
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
haskellPackages.tldr: fix build, add as a top-level package #29328
Conversation
|
||
# the tests for shell-conduit on Darwin illegitimatey assume non-GNU echo | ||
# see: https://github.com/psibi/shell-conduit/issues/12 | ||
doCheck = !pkgs.stdenv.hostPlatform.isDarwin; |
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.
It might be possible to remedy this issue by adding pkgs.coreutils
into testToolDepends
for this package so that GNU echo is in $PATH. It's not essential ... just an idea.
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.
The problem is the reverse: because GNU echo is on the path, the tests don't find the behavior they expect on Darwin with Nix.
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.
Ah, I see. Sorry, I misread the comment above.
# shell-conduit determines what commands are available at compile-time, so | ||
# that tldr will not compile unless the shell-conduit it uses is compiled | ||
# with git in its environment. | ||
buildInputs = oldAttrs.buildInputs ++ [ pkgs.git ]; |
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.
Please use lib.addBuildTool
to accomplish this instead of overrideAttrs
.
Thanks for your review! I've fixed it up now. J/w: besides making the code look better (simpler and more consistent), which is definitely worth something, are there additional benefits of using the |
I don't think there's any major benefit except readability. |
Thanks again! |
Motivation for this change
The package previously did not work (on any platform)
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)