Bug#862024: gstreamer1.0-plugins-bad: Dependency on libopencv-contrib3.2 pulls over 236MB.
slomo at debian.org
Sat Oct 21 08:14:22 UTC 2017
On Fri, 2017-10-20 at 22:16 +0200, Michael Biebl wrote:
> On Thu, 19 Oct 2017 22:35:33 -0300 Daniel Serpell
> <daniel.serpell at gmail.com> wrote:
> > Package: gstreamer1.0-plugins-bad
> > Version: 1.12.3-2
> > Followup-For: Bug #862024
> > Hi!
> > Biggest culprit are the new opencv packages, there libopencv-contrib3.2
> > pulls libvtk (150MB) and other big packages, about 236MB in total.
> > Next in the list is libopencv-calib3d3.2, at 60MB,
> > libopencv-objdetect3.2 at 58MB, libopencv-imgcodecs3.2 at 57MB.
> > So, simply splitting /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstopencv.so
> > out in another package will reduce the size of dependencies to the
> > previous level.
> Sebastian what do you think about splitting out less common used plugins
> with heavy dependencies into a separate binary package like
> The first plugin moved to this -extra package would be libgstopencv.so
> and we could move more plugins as we see fit (that's why I think using a
> rather generic name like -extra would be preferrable).
> The main gstreamer1.0-plugins-bad package would have a suggests:
I'm fine with the idea, the main problem is that whatever I decide for
"extra" plugins, for someone it will be a important one :)
Moving opencv to its own binary package was on my list already, its
dependency chain is just too huge and most people don't need it.
So let's go with an "extra" package instead, I'll spend some time
thinking about what else would make sense to have moved. DirectFB
> A middle ground would be to investigate why gstreamer1.0-plugins-bad
> needs libopencv-contrib3.2 with opencv and if this could be avoided.
Yes, we use some of the contrib stuff unfortunately.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 963 bytes
Desc: This is a digitally signed message part
More information about the pkg-gstreamer-maintainers