[mpd] micro is not micro

[hiro]

Hi, today I tried to setup a very basic install on my embedded device. My only wanted extension: mpd
tce-load downloads what feels like a debian of extensions which in my mind is a complete waste of space.
I only use a 32mb DOM for storage and don't it to get full (the reason for using microcore).
I'm now going to use the old tc 2.1, which had less bloated extensions.

We don't need extensions if every extension depends on everything but the kitchen sink.

[curaga]

It's true the current mpd.tcz has just about everything enabled. IIRC the consensus was to make a separate -minimal mpd extension.

edit: ref http://forum.tinycorelinux.net/index.php?topic=7295.0

[tinypoodle]

~25 MBb is a lot if storage available is 32Mb - whicy I could guess that it's practically less, usually storage space being calculated in decimal rather than binary terms, plus space needed by the file system (format).

No idea what your purpose of using mpd is, but did you look into possible alternatives to achieve your goals?

[hiro]

No idea what your purpose of using mpd is, but did you look into possible alternatives to achieve your goals?

Like I said, I'm back to using tc 2.1 now. And I'm of course using it to listen to music.

[hiro]

It's true the current mpd.tcz has just about everything enabled. IIRC the consensus was to make a separate -minimal mpd extension.

edit: ref http://forum.tinycorelinux.net/index.php?topic=7295.0

Perhaps you could make the old version mpd-minimal? I would compile it again, but I don't really see the need...

[curaga]

Perhaps you could make the old version mpd-minimal? I would compile it again, but I don't really see the need...

That would be an ok interim solution, until someone submits a native -minimal for 3.x. Ok, copied the 2.x mpd to 3.x as -minimal.

[tinypoodle]

No idea what your purpose of using mpd is, but did you look into possible alternatives to achieve your goals?

Like I said, I'm back to using tc 2.1 now. And I'm of course using it to listen to music.

Umm, that listening to music is involved somehow is implied, but for which reason exactly you need mpd for that task?
And where is the music stored? (as you say you have only 32MB of storage)

[gutmensch]

Apart from building a minimal version it would surely be an improvement if all dependencies (not to say extensions were strictly separated by lib, bin and dev. mpd doesn't need a lame en- or decoder or dbus static libs or libtool archives, just the libs. Same for fluidsynth, flac and so on. It would be good to have some script checking the repo for unstripped versions, too (I guess there are some). Overall from a quick glance I'd say it's definitely possible to minimize the dependency size by about 30% to 40%...

How about an extension auditing (auto generated) wiki page, which states extensions to be reworked?

[hiro]

All my music is stored in google mail.
If I didn't have mpd I would write some sh scripts for the same task, but as it runs very stable here and does everything I need I simply enjoy the music instead

[Jason W]

As for the scripted checking and stripping of extension contents, there is one concern I see.  "strip -g", which is what we use on libraries, leaves the file listed as "unstripped" when checked with the file command.  That would make for a lot of unneeded stripping of already stripped libs, though I don't know if that would cause an issue.   Also, some things like grub2 will not function if you strip it's files, though I am not sure if there are other packages like it.

I guess the relevent files could be copied, stripped, and then compared to the original to see if there was an md5 or size difference to determine if "strip -g" was already used on them.  But affecting extension contents without a reasonable means of testing the results makes me a little leery of it though.