ciphey 5.14.0 (new formula)

[alebcay]

• 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 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 --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[iMichka]

I'm working on a fix for the Linux CI.

[harens]

I added Ciphey to MacPorts and wrote a few things about packaging Ciphey (Ciphey/CipheyCore#17). I'm just going to have a quick look through the formula before it's merged if that's ok.

Also, congrats @alebcay on getting this working!

[harens]

Thanks @alebcay for doing this. I left a few notes that may or may not be applicable for Homebrew. Also just so you're aware, cipheycore requires C++20 if that makes any difference.

[iMichka]

@alebcay if you rebase this the Linux CI should be green, we do not build Linux bottles for new formulae (yet) here. I fixed the CI for that case.

[dawidd6]

Don't worry. No need to rebase, just rerun jobs.

[alebcay]

Thanks for the pointers, @harens. I've left the dev deps in for now. Since Homebrew doesn't have a notion of formula ownership, keeping all of the deps in makes future maintenance easier for people unfamiliar with the nature of which dependencies are actually needed, especially if Ciphey's dependencies change.

[harens]

LGTM. Thanks for submitting this @alebcay! 🎉

[BrewTestBot]

@nandahkrishna has triggered a merge.