2015-08-04 15:49 GMT+03:00 Reindl Harald <h.rei...@thelounge.net>: > > > Am 04.08.2015 um 14:25 schrieb Martin Sandsmark: >> >> On Tue, Aug 04, 2015 at 09:47:57PM +1000, Joseph Crowell wrote: >>> >>> Some of the codec dependencies are from non-free libraries with closed >>> source code. >> >> >> Which codecs/libraries are you talking about? >> >> >>> While other players utilize separate libraries and you can package them >>> for >>> download without crossing this precarious line, usually VLC has it's own >>> bundled codec libraries. >> >> >> Please point me to any libraries that VLC bundles, I can't find any > > > rpm -q --filesbypkg vlc-core | grep "\.so" > and that below is only a part >
That's rubbish, you can't check it that way, of course it will be compiled in a package... also probably all those libraries are open source. Download VLC source tarball and you'll see there 0 compiled binaries. As for licensing and patent issues distributions can (and probably do) remove those parts and compile --without-something, issue solved. Users who wish those features can replace their system package with their own compiled one or just add missing plugins or whatever. (some Fedora users use RPM Fusion repo for non-free packages) About media player as advanced power user (media collection in several TBs) I still haven't found any decent cross-platform media player, mostly choice is between beautiful UI but lack of features (there are plenty of such players) or somewhat feature full (VLC) but no good UI. Creating any kind of backend is pointless as any missing features would be better contributed to VLC, etc. so probably best would be just create a frontend for LibVLC (there's even VLC-Qt, http://vlc-qt.tano.si/) and when creating a frontend you could have multiple versions of it for different usage patterns, like very simple basic one and other powerful feature full. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
