If you wanted to keep it, you've had two years to take maintainership
and start fixing this mess. It's a bit late.

Some people should have read some documentation about threading before
they did 1000+ commits. Yes, I am obviously annoyed. I have been fixing
VLC for 18 months because of these "great former developers".

I assume nothing can ever try to add a new one once the interfaces have
been destroyed. If not there is a race condition.

opengllayer: Don't protect a module by #ifdef you'll end up in warnings. Disable it at configure time if needed.

Complete l10n to be done later on

Some (buggy?) thread implementations use RT signals internally...
The handling of SIGPIPE remains somewhat problematic. We should probably
use MSG_NOSIGNAL when writing to sockets, but this does not work when
dealing with pipes/FIFOs or writing to sockets using write(). In
particular, net_Write uses write() so that it can be used on non-socket
descriptors too (I believe this is used by the RC interface).

Though this should not happen as we are using non-blocking mode

Character device may be seekable (depending on the device) and block
device are seekable, but only on certain boundaries which we don't
handle.

Note to self: don't ever trust IB3

(only on supported platforms, being just Darwin right now)

Clean up the code a bit, turning to be half as laggy as the previous code, but it will need to be properly fixed.

Additionally, we are a good citizen now, since we actually quit our session instead of just releasing it. This takes a couple of secs though.

Use a ffmpeg revision which suits our state of patches

Please leave the FFmpeg revision fixed and only update it if you sure that your newer one is stable, nice and cool.

The jam-based target is removed by this commmit.

Finally upgrade the build target to a native one (in favour of a jam-based one, whose support is to be reomoved by Xcode's next release)

Regrettably, this adds yet another file where to change the VLC version

Unsure about my sanity now though.