GNOME Bugzilla – Bug 559431
Reduce the number of plugins without external dependencies
Last modified: 2016-05-28 18:11:17 UTC
Hi, in 0.11 we should definitely merge some plugins with external dependencies together into one. This makes sense because more shared objects a) need more time for the registry to check if it's up to date and b) need more memory and dynamic linking time at runtime. One example would be: audioconvert, audioresample, audiotestsrc, interleave, deinterleave merged into a single "basic audio elements" plugin.
What about a wiki page to gather possible collections.
Discussed with time and bilboed. They also see no big issue if we merge elements, especially if they are already in the same module.
This can always be done later as well, for what it's worth. We have renamed plugins in the past in 0.10 and moved elements from one plugin into another in 0.10 as well, so I don't see why we can't merge things during the stable cycle. I don't consider plugin <-> factory mappings as part of our ABI, and I'm not aware of problems (other than the ususal registry stuff when conflicting versions of plugin modules are installed).
I intend to consolidate some tag-related plugins in -base for 1.1.x, fwiw.
So what to do about this? Still planned, not deemed important enough?
Still planned, but not for 1.1.x :)
<bilboed> and we really should at least have mpegtsdemux and mpegtsmux code in the same location to avoid duplicated code :( <bilboed> (hell, maybe also mpegpsdemux ...) <slomo> yes, and PS
I don't think we need a bug for this..