[arch-dev-public] On pushing a standalone opencv 3.x
Hey folks
I apologize for the rather tardy package maintenance and management that's been going on for some time.
I had prepped opencv 3.x a long time ago, and it seems there is no point in waiting for third-parties to migrate. I had users requesting a separate package and a couple of them have helped test it.
If there are no objections, I'll go ahead and push 3.x, which should co-exist fine with 2.x. I suppose it's OK to break our naming convention in cases like these.
-- GPG/PGP ID: C0711BF1
Hi
On Fri, Dec 4, 2015 at 9:07 AM, Rashif Ray Rahman schiv@archlinux.org wrote:
If there are no objections, I'll go ahead and push 3.x, which should co-exist fine with 2.x. I suppose it's OK to break our naming convention in cases like these.
Why to break it? Just push new opencv and opencv-2 to staging and create a TODO to rebuild all the dependencies.
On 4 December 2015 at 23:20, Anatol Pomozov anatol.pomozov@gmail.com wrote:
Why to break it? Just push new opencv and opencv-2 to staging and create a TODO to rebuild all the dependencies.
I want to avoid a rebuild altogether because it's additional work for nothing, but seeing that there are not that many packages, I guess that's OK.
On 4 December 2015 at 23:41, Antonio Rojas arojas@archlinux.org wrote:
Have you checked if this is actually still needed? At least KDE packages (digikam, kipi-plugins, libkface) support opencv3 already.
Good point, I was going to run a rebuild again of the last few packages I checked before this. It'd still be good to hear from the maintainers of the other packages.
-- GPG/PGP ID: C0711BF1
On Fri, 2015-12-04 at 23:53 +0600, Ray Rashif wrote:
On 4 December 2015 at 23:20, Anatol Pomozov <anatol.pomozov@gmail.com
wrote: Why to break it? Just push new opencv and opencv-2 to staging and create a TODO to rebuild all the dependencies.
I want to avoid a rebuild altogether because it's additional work for nothing, but seeing that there are not that many packages, I guess that's OK.
We can handle this rebuild with Evangelos' arch-rebuild script. Shouldn't take long with usual people participating.
BP
On Sat, Dec 5, 2015 at 11:57 AM, Bartłomiej Piotrowski bpiotrowski@archlinux.org wrote:
We can handle this rebuild with Evangelos' arch-rebuild script.
Only if it is a simple pkgrel bump; the discussed rebuild seems to require packages switching over to a new opencv2 package, in which case it is better to do it manually (it's quite small too, around 10 packages).
On 5 December 2015 at 16:15, Evangelos Foutras evangelos@foutrelis.com wrote:
On Sat, Dec 5, 2015 at 11:57 AM, Bartłomiej Piotrowski bpiotrowski@archlinux.org wrote:
We can handle this rebuild with Evangelos' arch-rebuild script.
Only if it is a simple pkgrel bump; the discussed rebuild seems to require packages switching over to a new opencv2 package, in which case it is better to do it manually (it's quite small too, around 10 packages).
Right. We'll begin when staging is clear, I'll edit the TODO. I'll find some time to check the build status again of the packages.
On 2015-12-21 20:20, Ray Rashif wrote:
Right. We'll begin when staging is clear, I'll edit the TODO. I'll find some time to check the build status again of the packages.
Looks like it doesn't overlap with our sandcastles made of Boost 1.16.0 rebuild, so I think it's fine to start it right away if you have prepared an upgrade of opencv and a new opencv2 package.
Bartłomiej
On 22 December 2015 at 04:20, Bartłomiej Piotrowski bpiotrowski@archlinux.org wrote:
Looks like it doesn't overlap with our sandcastles made of Boost 1.16.0 rebuild, so I think it's fine to start it right away if you have prepared an upgrade of opencv and a new opencv2 package.
Thanks for taking this forward and getting this rebuilt once and for all!
Some of you may have received e-mails from a helping user Gabriel regarding some fixes here and there, but otherwise note that 3.x was also committed once before so look at that for any further context if needed. [1]
[1] https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages...
On 2016-03-11 21:06, Rashif Ray Rahman wrote:
On 22 December 2015 at 04:20, Bartłomiej Piotrowski bpiotrowski@archlinux.org wrote:
Looks like it doesn't overlap with our sandcastles made of Boost 1.16.0 rebuild, so I think it's fine to start it right away if you have prepared an upgrade of opencv and a new opencv2 package.
Thanks for taking this forward and getting this rebuilt once and for all!
Some of you may have received e-mails from a helping user Gabriel regarding some fixes here and there, but otherwise note that 3.x was also committed once before so look at that for any further context if needed. [1]
[1] https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages...
Everything has been rebuilt more or less fine thanks to Antonio's awesome help. One remaining bit is either fixing gst-plugins-bad with OpenCV 3.1 or packaging OpenCV 2 for the same reason.
BP
Rashif Ray Rahman wrote:
If there are no objections, I'll go ahead and push 3.x, which should co-exist fine with 2.x. I suppose it's OK to break our naming convention in cases like these.
Have you checked if this is actually still needed? At least KDE packages (digikam, kipi-plugins, libkface) support opencv3 already.
participants (6)
-
Anatol Pomozov
-
Antonio Rojas
-
Bartłomiej Piotrowski
-
Evangelos Foutras
-
Rashif Ray Rahman
-
Ray Rashif