In theory, we should check that there is only one slash per token, but
it is not really dangerous.

First, we should not let user shoot themselves in the foot. But most
importantly, we need to validate the string as it is marked as a safe
option (especially CRLF there could be disastrous).

RFC2616 requires a space-separated list of names[/versions]

The new config value is duplicated, and the copy is stored to the
configuration. After the configuration R/W lock is released, we have no
warranty that another thread does not change the same configuration
item, and free our own copy. Admittedly, this is very unlikely.

Instead, we can simply pass the original string from the caller to the
callback - that one must remain valid through the config_PutPsz()
function call by definition.

And remove patch applied upstream. Keep the same change as libebml for win32 buildsystem

Remove 2 patches applied upstream, add another one :)

See #3613

VLC would not be redistributable.

The LUA interface is unmaintained, enough waiting.
Works around #3623, #3627, #3687, #3691.

Otherwise we cannot render videos with X11 (and fallback to
non-embedded SDL or ASCII).

Signed-off-by: Christophe Mutricy <xtophe@videolan.org>

Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

Signed-off-by: Laurent Aimar <fenrir@videolan.org>

... so that waitpid() works even if our parent process ignores SIGCHLD
(SIG_IGN is preserved across exec*()).

Signed-off-by: Ilkka Ollakka <ileoo@videolan.org>

I don't understand why the test would be needed, you do receive data
only if the ES is selected.

This was broken after the extension merge.
Close #3665

I highly doubt that the osd register/clear functions are usable...

It removes two broken vlc_object_find(INPUT, PARENT) and fixes input
attachements support when the vout is reused.

It allows to retreive input attachments.