- Update the packaging files.
- Rename libvlc2.install - libvlc5.install
- Rename libvlc2.symbols - libvlc5.symbols
- Rename libvlccore2.install - libvlccore5.install
- Rename libvlccore2.symbols - libvlccore5.symbols

Conflicts:
	debian/patches/series
	debian/rules
	debian/vlc-nox.install
	debian/vlc-plugin-ggi.install
	debian/vlc-plugin-jack.install
	debian/vlc-plugin-pulse.install
	debian/vlc-plugin-sdl.install
	debian/vlc-plugin-svg.install
	debian/vlc-plugin-svgalib.install
	debian/vlc.install

Download the first couple of segments to determine the best
bandwidth match and to ensure smooth playback.

The plugins path of vlc-1.X changed wrt to earlier versions.

Add patch for splice point generation in muxing TS streams.

Put debian directory under source control for creating debs.

Move logging of current segment and stream. The previous place gave
confusing information.

After the adaptive bandwidth changes seeking could end up in a segment
that is not available. Each segment is downloaded once and after switching
to higher or lower bandwidth segments downloaded for previous bandwidths
will not be deleted or downloaded. The later is to be fixed.

Start playback with the lowest bandwidth stream.

NextSegment() assumed that the download thread its hls_stream_t was leading.
However this was too simplistic.

NextSegment() seeks the segment in *any* of the hls_stream_t, assuming that
each segment will be downloaded only once.

Test script for traffic shaping with tc (iproute).

Download the next segment from a playback standpoint.

Cleanup NextSegment().

The bandwidth calculation needed corrections and is less agressive in
switching to higher bandwidths.

(It was broken by a8e4b30b)

Move the definition to qt4.hpp and add a comment

If you want to use #description, you need to set up the appropriate
struct on pass it down as a variable

This also fixes error handling: if the thread cannot be created, we do
fail cleanly.

This allows using it at another time than destroying the object

...and less prone to deadlocks. This restarts until all keys are NULL,
in case cleaning up reset one key back to a non-NULL value.
There is still a slight difference with POSIX still. POSIX will restarts
only after all destructors have been invoked, not after the first one.