8000 Remove OpenSSL provider from Botan formula by securitykernel · Pull Request #57540 · Homebrew/homebrew-core · GitHub
[go: up one dir, main page]

Skip to content

Remove OpenSSL provider from Botan formula #57540

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&rdq 8000 uo;, 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

Closed

Conversation

securitykernel
Copy link
Contributor

The authors do not recommend building with
OpenSSL support. Additionally, they recommend
building with sqlite support.

See https://botan.randombit.net/handbook/packaging.html.

  • Have you followed the guidelines for contributing?
  • [x ] Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with 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 brew install <formula>)?

Formula/botan.rb Outdated
@@ -14,7 +14,7 @@ class Botan < Formula

depends_on "pkg-config" => :build
depends_on :macos # Due to Python 2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this still true? The configure script suggests it should work with python 3.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upstream maintainer here. The configure script absolutely works with Python3 (we are maintaining 2+3 compat for the time being, though will eventually move to Python3 only)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@securitykernel could you amend your PR to make it use python@3.8 then instead of depending on macOS?

8000
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You might need to set the python version cause it's installing python 2.7 bindings right now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. Updated.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SMillerDev Rebased onto master (2.15.0 version bump). Ready for merge IMHO.

@securitykernel securitykernel force-pushed the botan-without-openssl branch 4 times, most recently from 46343a8 to c503093 Compare July 8, 2020 06:24
@SMillerDev
Copy link
Member

LGTM, @securitykernel could you please rename your commit to say <formula>: <reason>

@SMillerDev SMillerDev added the almost there PR is nearly ready to merge label Jul 8, 2020
@securitykernel securitykernel force-pushed the botan-without-openssl branch from c503093 to 22f900c Compare July 9, 2020 05:41
@securitykernel
Copy link
Contributor Author

@SMillerDev Renamed the commit.

Copy link
Member
@SMillerDev SMillerDev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @securitykernel ! Without contributions like yours it'd be impossible to keep homebrew going with the high standards that users have come to expect from the project. You can feel good knowing that you've made the world a tiny bit better for homebrew users around the world! 👍 🎉

@BrewTestBot
Copy link
Member

🤖 A scheduled task has triggered a merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
almost there PR is nearly ready to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0