Hi, > Thanks to all for the replies, I would like to ask if OpenCV could be > proposed as an accepted dependency by IPOL, since it is a widely used > library in the field of image processing.
First, I am not an OpenCV user, so everything I write may be wrong and could need to be corrected (and I'd be glad to be corrected). The problem with OpenCV is the API stability. Version 1 was released in 2006, version 2 in 2009, and code written for OpenCV 1.x could not be compiled with OpenCV 2.x. Since OpenCV i.x is not maintained anymore, not even distributed, if IPOL had accepted code depending on OpenCV in 2009 it would be broken today and this would defeat the purposes of IPOL (if the code is broken, you can't verify, reuse and/or compare it). The OpenCV project management has changed in 2009 and again in 2012, and I find nowhere on the project website a statement that they value to have some API stability. In these conditions it seems risky to accept in IPOL some code using OpenCV and expecting the library to be availavble on the system. > The code to be submitted also depends on GSL and BOOST, but these can be > included on the package to be submitted. Why couldn't you include the OpenCV code as well? PS: All that is in the context of the current IPOL software restrictions. A relaxed policy has been proposed at the Treilles meeting, but I think we are not yet at the point where this can become the main IPOL policy. -- Nicolas LIMARE http://nicolas.limare.net/ pgp:0xFA423F4F
signature.asc
Description: Digital signature
-- IPOL - Image Processing On Line - http://ipol.im/ contact [email protected] - http://www.ipol.im/meta/contact/ news+feeds twitter @IPOL_journal - http://www.ipol.im/meta/feeds/ announces [email protected] - http://tools.ipol.im/mm/announce/ discussions [email protected] - http://tools.ipol.im/mm/discuss/
