Seems xvmc is optional in libxcb, so why keep it enabled by default? It is obsolete: only supports mpeg2 and mpeg4 asp codecs, but not h.264 or HEVC >>> Configuring source in /var/package-manager/tmp/portage/x11-libs/libxcb-1.10/work/libxcb-1.10 ... ... Package: libxcb 1.10 Configuration XDM support.........: yes sendmsg fd passing..: yes Build unit tests....: no with html results.: no XCB buffer size.....: 16384 X11 extensions ... xvmc................: yes $ equery f x11-libs/libxcb|grep xvmc -c 44
I'm unaware of libxcb's xvmc code being used for anything. If we do anything with it, we should just turn it off. But, I don't really think we should bother.. More justification needed.
So what is the problem with turning it off? I can provide and test patch for ebuild if required. I really would like to remove xvmc from my systems completely, because nothing is using it: $ grep -i xvmc /var/db/pkg/*/*/NEEDED.ELF.2 /var/db/pkg/x11-libs/libxcb-1.10/NEEDED.ELF.2:X86_64;/usr/lib64/libxcb-xvmc.so.0.0.0;libxcb-xvmc.so.0;;libxcb.so.1,libc.so.6 When running KDE X11 session and playing mpg files with vlc and mpv: # lsof -n|grep -i xvmc
The library is 14KB. Does it really matter?
When entirely removing obsolete API from system, size of particular component does not matter: it should be removed anyway.
