openalpr: deprecate

[bayandin]

• 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>?

---

The latest release of openalpr was in 2016, the formula already patched (with upstream changes) to support the latest versions of dependencies.
It started to give us some troubles in tesseract (#90220) and opencv (#89948) updates.

==> Analytics
install: 91 (30 days), 281 (90 days), 906 (365 days)
install-on-request: 91 (30 days), 281 (90 days), 905 (365 days)
build-error: 10 (30 days)

[carlocab]

Can we switch it back to opencv@3 and deprecate it? We should at least try to have a deprecation period.

[bayandin]

Can we switch it back to opencv@3 and deprecate it?

Why? It'll stop working with the next version of tesseract anyway.

[SMillerDev]

Why? It'll stop working with the next version of tesseract anyway.

Because that will give people a window to notice the deprecation

[bayandin]

Why? It'll stop working with the next version of tesseract anyway.

Because that will give people a window to notice the deprecation

Ah sorry, my question was rather about Can we switch it back to opencv@3 part.

Changed disable to deprecate.