Xext: disable Xv and XvMC extension by default

[metux]

Disable the Xv and XvMC extensions by default, but they still can be enabled explicitly.

Signed-off-by: Enrico Weigelt, metux IT consult [email protected]

See discussion: https://github.com/orgs/X11Libre/discussions/336

[stefan11111]

I don't think this is a good idea. Xv is still used by mpv.

[metux]

I don't think this is a good idea. Xv is still used by mpv.

IIRC, mpv never actually had it. (it does have GPU acceleration, but not via Xvmc)

[stefan11111]

I don't think this is a good idea. Xv is still used by mpv.

IIRC, mpv never actually had it. (it does have GPU acceleration, but not via Xvmc)

It does have --vo=xv

[metux]

I don't think this is a good idea. Xv is still used by mpv.

IIRC, mpv never actually had it. (it does have GPU acceleration, but not via Xvmc)

It does have --vo=xv

that's xv, not xvmc.

xvmc is for motion compensation (and iDCT), that's not output, but part of the decoding process, one of the steps done for generating the next final frame from the previous one. Completely tied to MPEG2 main profile. For anything else, not practically usable.

[stefan11111]

I don't think this is a good idea. Xv is still used by mpv.

IIRC, mpv never actually had it. (it does have GPU acceleration, but not via Xvmc)

It does have --vo=xv

that's xv, not xvmc.

This pr disables Xv by default.

[metux]

I don't think this is a good idea. Xv is still used by mpv.

IIRC, mpv never actually had it. (it does have GPU acceleration, but not via Xvmc)

It does have --vo=xv

that's xv, not xvmc.

This pr disables Xv by default.

Yes. It can be easily enabled at server startup time.

[callmetango]

If we choose to accept this change than we have to make this very clear to our users. Think release notes, notable changes, etc. Otherwise it could be perceived as "XLibre does not work." Even if the user base could be very small.

[metux]

If we choose to accept this change than we have to make this very clear to our users. Think release notes, notable changes, etc. Otherwise it could be perceived as "XLibre does not work." Even if the user base could be very small.

Of course, this will be in the release announcement (I'm still doing those the bigger releases ;-)) When the decision is made, we're also announce this on the mailing list.

[smj-cc]

For reference, in the current ::gentoo repository:

No package enables the xvmc use flag by default, nor does any package depend upon x11-libs/libXvMC without that flag set.

Only media-libs/xine-lib, media-video/mplayer, and games-emulation/snes9x enable the xv use flag by default, and the only packages which depend upon x11-libs/libXv without that flag set are:

media-video/ffmpeg, media-video/ffmpeg-compat, x11-wm/windowmaker, media-video/xine-ui, media-libs/libmpeg2, media-libs/gst-plugins-base, x11-misc/virtualgl, and of course x11-libs/libXvMC.

Also of note:

sci-geosciences/google-earth-bin depend upon media-libs/gst-plugins-base.

Caveat: I have found that some ebuilds declare dependencies which the software can successfully compile and run without.

Edit: google-earth-bin and ffmpeg appear to function with x11-libs/libXv forcibly unmerged.