thumbor-9999.ebuild: Hard-code OpenCV Python version

media-libs/opencv uses python-single-r1, which means it doesn't like
our ${PYTHON_USEDEP}:

  emerge: there are no ebuilds built with USE flags to satisfy
  "media-libs/opencv[python_targets_python2_7(-)?,-python_single_target_python2_7(-)]".

Note the '-' in front of python_single_target_python2_7.  I'm not sure
what the best way to handle this is, since *without* the OpenCV
dependency, Thumbor could theoretically be installed for multiple
Python versions simultaneously.  It would be nice to translate the
OpenCV ebuild to python-r1 or distutils-r1, but it ties the Python
binding config into its main CMake setup:

  local mycmakeargs=(
    ...
    $(cmake-utils_use_build python opencv_python)
    ...
  )

That makes it hard to step in and build Python bindings for a
different version.  Until someone thinks up (or tells me about) a
cleaner way to handle this, I'm just going to hardcode the
single-version we need.

diff --git a/thumbor-9999.ebuild b/thumbor-9999.ebuild
index 011aeacbeeda6089d36c60939b8b86ba0779ae9f..71e3113a1df7ad9969eda92e1948a10e5b3f12da 100644 (file)
--- a/thumbor-9999.ebuild
+++ b/thumbor-9999.ebuild
@@ -33,7 +33,7 @@ RDEPEND="
        >=dev-python/python-magic-0.4.3[${PYTHON_USEDEP}]
        >=dev-python/thumbor-pexif-0.14[${PYTHON_USEDEP}]
        <dev-python/thumbor-pexif-1.0[${PYTHON_USEDEP}]
-       media-libs/opencv[${PYTHON_USEDEP}]
+       media-libs/opencv[python_single_target_python2_7]
        >=www-servers/tornado-2.3.0[${PYTHON_USEDEP}]
        <www-servers/tornado-3.3.0[${PYTHON_USEDEP}]
        "