Network support is essential or expected for quite a lot of applications relying on libav/ffmpeg. For example, users, trying to migrate from mplayers (with+network) to mpv (which silently assumes you have ffmpeg implementation with network support) results in "mplayer2 can, mpv can't" situation. Network support requires no additional dependencies and seems not to increase build time. So I propose making `network` flag an enabled-by-default one for both ffmpeg implementations.
I agree, network support in ffmpeg/libav is required for playing any http and udp streams, this is something expected to work by default. Also recently I had several reports from users not able to play youtube or iptv videos because their libav copy was compiled without USE network enabled. When ffmpeg is installed mpv will print error if some protocol is not supported: [ffmpeg] Protocol not found. Make sure ffmpeg/Libav is compiled with networking support. but when libav is used instead of ffmpeg, mpv will not print any error because of libav bug: https://bugzilla.libav.org/show_bug.cgi?id=577
from #gentoo-media: <lu_zero> about making it +network <lu_zero> sounds fine to me ... <Nikoli> aballier, so what do you think about +network for ffmpeg? <aballier> Nikoli: wfm <aballier> one of the few useflags worth +ing
+ 26 Oct 2013; Alexis Ballier <aballier@gentoo.org> ffmpeg-0.10.9.ebuild, + ffmpeg-1.0.7.ebuild, ffmpeg-1.0.8.ebuild, ffmpeg-1.2.3.ebuild, + ffmpeg-1.2.4.ebuild, ffmpeg-2.0.2.ebuild, ffmpeg-9999.ebuild: + enable network useflag by default, bug #488762 +
Libav is still not fixed.
(In reply to Nikoli from comment #4) > Libav is still not fixed. Derp. I was somehow looking for the wrong USE flag. Thanks, man. Fixed in CVS.
