[MacPorts] #37276: Kinect support in OpenCV: openni-devel (submission), openni-devel-sensorkinect (submission), opencv (enhancement), openni (enhancement)

[MacPorts]

#37276: Kinect support in OpenCV: openni-devel (submission), openni-devel-
sensorkinect (submission), opencv (enhancement), openni (enhancement)
-------------------------------------+-------------------------------------
  Reporter:  josephhowse@…           |      Owner:  macports-tickets@…
      Type:  submission              |     Status:  new
  Priority:  Normal                  |  Milestone:
 Component:  ports                   |    Version:  2.1.2
Resolution:                          |   Keywords:  Kinect OpenCV OpenNI
      Port:  openni-devel openni-    |  SensorKinect
  devel-sensorkinect opencv openni   |
-------------------------------------+-------------------------------------

Comment (by josephhowse@…):

 Thanks for the feedback. Here is some additional information that might
 address some of your comments. I'm happy to follow whatever naming
 convention is appropriate for the ports and variant.

 SensorKinect depends on unstable versions of OpenNI (1.5.4.0, 1.5.2.7,
 1.4.0.2, etc.).

 > Note that we had an existing request to add an openni variant to the
 opencv port in #35512. Does this patch satisfy that request?

 > we don't typically depend on -devel ports

 An +openni variant was already added to opencv in a recent update. The
 difference between +openni_devel_sensorkinect (my submission) and the
 existing +openni variant is that +openni_devel_sensorkinect also supports
 Kinect via SensorKinect. Due to SensorKinect's dependency on an unstable
 OpenNI version, +openni_devel_sensorkinect depends on openni-devel,
 whereas +openni depends on (stable) openni.

 > The conflicts keyword takes bare port names, not dependency specifiers,
 so it should be "conflicts openni", etc.

 Do you mean that "conflicts port:openni" should be "conflicts openni" (in
 the openni-devel Portfile)?  Or is there some problem with the use of
 "conflicts" in "variant openni_devel_sensorkinect conflicts openni" (in
 the opencv patch)?

 > It would be better to fix the tbb port; see #35990.

 If the tbb port is being fixed, then, yes, the proposed change to the
 opencv +tbb variant can be dropped.

-- 
Ticket URL: <https://trac.macports.org/ticket/37276#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS