Splitting libav-tools

Reinhard Tartler siretart at gmail.com
Sat Mar 24 07:18:06 UTC 2012


On Sat, Mar 24, 2012 at 1:19 AM, Andres Mejia <amejia004 at gmail.com> wrote:
> I believe the libav-tools package should be split and the separate
> binary programs each be installed in their own package. Out of all the
> programs from libav/ffmpeg, I've rarely used ffplay, and I never used
> the server or probe programs.

I've been thinking about this as well, but TBH, I don't really see the
gain. Splitting avplay out of libav-tools would save 17 library
dependencies:
+libasyncns.so.0
+libcaca.so.0
+libdbus-1.so.3
+libFLAC.so.8
+libjson.so.0
+libncursesw.so.5
+libnsl.so.1
+libpulsecommon-1.1.so
+libpulse-simple.so.0
+libpulse.so.0
+libresolv.so.2
+libSDL-1.2.so.0
+libslang.so.2
+libsndfile.so.1
+libtinfo.so.5
+libwrap.so.0

In particular, it would not save you from X11 related dependencies,
thanks to the libva.

TBH, I'm not entirely convinced that there is much gain in splitting
these. If we do it, libav-tools should stay as meta package that
depends on all three tiny packages.


> It would also help if the server be it's
> own package, complete with sysvinit (or systemd or upstart) scripts.

avserver is not really useful without proper configuration. You need
to tell it what kind of streams to provide on what port, etc. For this
reason, I'm not even sure if providing a conffile in
/etc/avserver.conf is a great idea. Maybe we should move it from /etc/
to /usr/share/doc/avserver/avserver.conf or something. In that place
we, could then also install example start up scripts.


-- 
regards,
    Reinhard



More information about the pkg-multimedia-maintainers mailing list