On Mon, Jul 16, 2018 at 2:12 AM, Sinan H <sinan(a)haliyo.net> wrote:
> I was referring to system resources needed to play music - not
how many
Mb
> you needed to download the
> software and associated dependencies (which will vary on many factors).
>
> As far as program size required for the named package:
>
> amarok is 5.3Mb
> amarok-libs is 2.6Mb
> amarok-utils is 61k
>
well, in any case, qmmp (which I like by the way) pulls wildmidi-libs,
which pulls fluid-soundfont-lite-patches amounting to 140MB. These would
have to be included in the liveimage, unless the maintainer can be
persuaded to build without midi support.
As a side note, current amarok master is on Qt5. There is no release yet
but people report stable behavior. How about erring on the side of bleeding
edge ?
_______________________________________________
An extra 140MB in the grand scheme of things is nothing IMHO. I believe
the more important thing here is to choose an application which is rock
solid, does the job and most importantly has a solid history of support.
juk and amarok do not meet the last criteria. Yes, after years of neglect
both are now getting some renewed attention, but qmmp has a very solid
record on this.