[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: OpenCV C-API support




Le 07/12/17 à 22:55, Dima Kogan a écrit :
Hi all.

So it looks like the OpenCV people have pretty much abandoned their C
API, to the point where trivial applications no longer build:

   https://github.com/opencv/opencv/issues/6221
   https://github.com/opencv/opencv/issues/8658
   https://github.com/opencv/opencv/issues/10246

They're uninterested in keeping this running, but this breaks a lot of
legacy applications. I think we (Debian) should keep this working if
possible.
How many packages are depending on OpenCV at the moment?
There're two approaches:

1. Update the packaging to (at least) make OpenCV2 available in sid, and
    at best also make it co-installable with OpenCV3.
We should consider the maintenance cost of keeping both of them in the archive.

Do we really have to keep cv2?
2. Patch our build of OpenCV3 that works with the older API. Right now,
    this actually is simple (I think). We'd just need to move the
    definition of cvRound() to C header instead of a C++ one. I'm sure
    there're details to be worked out, but it LOOKS easy. With time,
    these updates could become difficult, but not yet.
It might not stay that simple in the future.

Again, that's part of evaluating the risks of taking on ourselves the maintenance burden.

Usually, if upstream does not care, I believe we should not either.

I favor option 2. Any strong opinions either way? If I don't hear any
complaining, I'll get the patches ready, and then talk about an actual
upload.

dima

If some legacy packages fail to keep up with the development of OpenCV, then they should probably rely on a different distribution mechanism than Debian. It's unfortunate upstream did not commit to keep a stable C-API, but downstreams should also inform themselves and adapt as part of their risk assessment.

My 2 cents,
Ghis


Reply to: