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
datefudge: work correctly even if GNU date is not in PATH #94045
Conversation
Why not go for a patchless approach and use |
I agree with @dasJ, please wrap the program. |
ba29fcb
to
f9bed8f
Compare
@SuperSandro2000 @dasJ Applied changes. |
@@ -1,4 +1,4 @@ | |||
{ stdenv, fetchgit, fetchpatch }: | |||
{ stdenv, lib, fetchgit, fetchpatch, makeWrapper, coreutils ? null }: |
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.
I would prefer if we just always pass in coreutils if this is possible. It would make this file less complex and coreutils is likely already downloaded anyway.
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.
On build system -- yes, coreutils is part of stdenv. On host system -- not necessary.
Result of 1 package built:
|
I marked this as stale due to inactivity. → More info |
Examples in manual assumes advanced features from date(1) like "last Friday", which only available in GNU coreutils version of date(1) utility. Without this patch, most examples from datefudge(1) manual will fail in busybox environment, which is confusing.
f9bed8f
to
4036434
Compare
Any chance to merge it as I wrote it? I still maintain that avoiding unnecessary dependency worth two conditional statements. @SuperSandro2000 |
Examples in manual assumes advanced features from date(1) like "last
Friday", which only available in GNU coreutils version of date(1)
utility. Without this patch, most examples from datefudge(1) manual will
fail in busybox environment, which is confusing.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)