-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Get rid of the Perl dependency #341
Comments
👍 to rewrite in C++ |
👍! Just to have an idea of the scope:
and
|
👍 |
3 similar comments
+1 |
👍 |
+1 |
Would also get rid of #19 |
👍 obviously. Seems like it wouldn't have to be a monolithic work item. I'm guessing many of the *.pm files are just wrapping functionality that's already in the C++ library, so some of that wouldn't even be necessary anymore. The individual utilities could be replaced one at a time if someone didn't want to take on the entire task at once. |
I'm on |
Yay! |
🍺 |
I'm now on find-runtime-roots.pl |
Rather than replacing it with an external C++ program, please add it directly to |
I've added a 50$ bounty for this issue at https://www.bountysource.com/issues/4399291-get-rid-of-the-perl-dependency |
Is there a bounty service that doesn't require sign-up? I'd like to support, but I don't want yet another account on some web service... |
You can login with github account. But no :) On Sat, 7 Nov 2015, 10:17 Bjørn Forsman notifications@github.com wrote:
|
And you can always make promises without any service at all... |
Ah, I didn't know bountysource was "a promise", I thought it was direct payment. |
Well, maybe, but I think there's an unavoidable tricky point: who decides that the issue is solved well-enough? |
Also, what if multiple people solve it? |
The one offering the bounty decides how the money should be split. |
|
nix-channel in #1026 |
@shlevy Thank you! I just added another $50 to the bounty. https://www.bountysource.com/issues/4399291-get-rid-of-the-perl-dependency Don't forget to claim it when it is complete. |
I consider the core work finished (if all PRs are merged and a simple final Makefile tweak added on top, nix on Linux has no dependency on perl) and the bounty is linked to this github issue. Any objections to me closing the issue to claim the bounty, and using the |
@shlevy sure, if PRs are merged and Nix can compile without perl, feel free to claim this :) |
I understood it as a suggestion to close/claim before merging the PRs. |
@vcunat No, the issue is solved for me when every change is merged in master. (and properly works together) |
OK, thought I'd check 😄 |
@shlevy I'd say you have done your part of the work so it's fine if you collect the bounty. |
@domenkozar Do I have to do anything besides just close the issue? |
I think you have to claim bounty on bountysource manually. |
From https://github.com/bountysource/core/wiki/Frequently-Asked-Questions it looks like the only way is to close the issue, maybe even the only way is to merge a commit that closes the issue. I will try closing this, let me know if you get the confirmation email. |
I needed to refresh about 6 times before you showed up as a claimer on https://www.bountysource.com/issues/4399291-get-rid-of-the-perl-dependency, but it's accepted from me. I'll try to write up a summary for all chip-in-ers :) |
Did my summary not show up? |
Nope |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/java-nix-reproducibility/13825/13 |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2023-10-23-nix-team-meeting-minutes-97/34561/1 |
…hix/cachix-action-11 chore(deps): bump cachix/cachix-action from 10 to 11
I.e. rewrite nix-build, download-from-binary-cache etc. in C++.
Darwin:
The text was updated successfully, but these errors were encountered: