Main Inclusion Report for opencv

Requirements

1. Availability: http://archive.ubuntu.com/ubuntu/pool/universe/o/opencv/; available for all supported platforms

2. Rationale:

   • Build dependency of kipi-plugins (provides batch Red Eyes Removal tool to KDE photo applications)

3. Security:

   • CVE entries: none

   • Secunia history: none

   • No binaries running as root or suid/sgid. No daemons.
   • Network activity: does not open any port. Does not handle incoming network data.
   • OpenCV library does process photo/video (binary) data streams and does computer vision analysis. This data is provided by calling application (in this case KDE photo application using kipi-plugin).
   • No source code review performed.

4. Quality assurance:

   • Always works out of box without configuration.
   • No debconf questions.

   • Debian bugs: only wishlist/normal, nothing of importance

   • Maintenance in Debian is vigorous

   • Upstream is vigorous (1.1-pre1 available, planned for 06-2009)

   • Upstream bug tracker: mostly for 1.1-pre1, 1.0 is considered stable

   • Hardware: OpenCV provides camera capture interface through library interface.
   • There is testcase suite in the package, but it does not look that it gets executed during build.

5. UI standards:

   • Does not provide UI (library).

6. Standards compliance:

   • FHS, Debian Policy compliant.

   • Debian library packaging guide standards compliant

   • Packaging system: debhelper Patch system: quilt

7. Dependencies:

   • debhelper (>= 5.0), quilt, libavcodec-dev (>= 0.svn20080206), libavformat-dev, libgtk2.0-dev, libjasper-dev, libjpeg62-dev, libpng12-dev, libraw1394-dev, libtiff4-dev, zlib1g-dev, python-dev, swig, python-support (>= 0.4.1)

   • Are these all in main ?

8. Maintenance:

   • Based on existing Debian experience, it is expected to have low maintenance. KIPI-Plugin developer is also following 1.1-pre1 development and it ensures that kipi-is compatible (no API changes for now).

   • There is Debian Scientific Team that is taking care of the package.

9. Background information:

   • The general purpose and context of the package should be clear from the package's debian/control file. If it isn't then please explain.
   • Upstream naming is consistent (OpenCV), while Debian packages uses shorter version (libcv-dev, libcv1...)

10. Internationalization:

    • No UI.

Reviewers

MIR bug: https://launchpad.net/bugs/324523

LukaRenko (Lure @ IRC, lure @ LP)