rip2 0.9.0 (new formula)

[bkaplowitz]

provides maintained version of rip under new rip2 name with new features.

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

It fails no fork but otherwise passes. As mentioned the original rip repo has not been maintained since 2020 and was previously listed under rm-improved or rip names.

[github-actions]

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

[bkaplowitz]

thanks for fast reply. Resolved the issues indicated above.

[bkaplowitz]

Okay, changes above should be fixed. It is failing on CI for audit it seems.

[chenrui333]

you can use generate_completions_from_executable(bin/"rip", "completion") for these three

[chenrui333]

since rip (aka rm-improved) is not maintainable, we can do something like rip@1 and rip kind of thing (which we did with gdrive #154959), this way, we dont need to include conflicts resolution.

[chenrui333]

never mind, it is not quite applicable in here:

• rip in cargo registry is called rm-improved, while rip2 is called rip2 (no naming consistency)
• the last rip release is 0.13.1, while rip2 is 0.9.0 (actually version downgrade)