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
dazel: init at 0.0.36 #65377
dazel: init at 0.0.36 #65377
Conversation
@@ -0,0 +1,19 @@ | |||
{ stdenv, buildPythonApplication, fetchPypi }: | |||
buildPythonApplication rec { | |||
version = "0.0.36"; |
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 can see 0.0.36 is the latest version in Pypi ( https://pypi.org/project/dazel/ ), but that is ~16 months behind the releases in Github: https://github.com/nadirizr/dazel/releases .
I don't think we should package outdated software, and instead should either work with upstream to update Pypi, or we should build from the Github repo itself.
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 agree with @tomfitzhenry that we should package the latest release.
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
I marked this as stale due to inactivity. → More info |
Motivation for this change
Introduce dazel.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)