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

radare: remove #51481

Merged
merged 1 commit into from Dec 3, 2018
Merged

radare: remove #51481

merged 1 commit into from Dec 3, 2018

Conversation

Mic92
Copy link
Member

@Mic92 Mic92 commented Dec 3, 2018

This project has been deprecated in 2016.
Radare2 should been used instead: https://github.com/radare/radare

cc @viric

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@Synthetica9
Copy link
Member

Maybe do radare = radare2?

This project has been deprecated in 2016.
Radare2 should been used intead: https://github.com/radare/radare
@Mic92
Copy link
Member Author

Mic92 commented Dec 3, 2018

I would not do that in this case. This could lead to confusion. This is not just a release. It is like a different software project. Also all binaries carries a 2 in its name i.e. r2, rabin2, radiff2. When they talk about the software in presentations they also always say radare2 instead of just radare.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants