Our MySQL 5.1 build is 50 MiB, while 5.5 is 152 MiB. It's mostly in the bin directory, which is 110 MiB. Apparently MySQL does some very bad static linking (for instance, the trivial MySQL utilities "replace" and "resolveip" are both almost 3 MiB).
@edolstra Have you looked into this? Will it make it into 14.04?
On a side note, mysql is such big also on other distros. Another thing is that binaries are not stripped for some reason, though stripping saves very little disk space (e.g. 3.2m instead of 3.3m for the mysql executable).
I think the answer is obvious, it was bought by Oracle 😬.
Is this still relevant?
Now we have a bloated mariadb instead (by default) :-) but it's not too bad anymore:
(EDITed: I didn't give du enough time for the files to settle, i.e. likely free reserved extents.)
mysql55: remove lib/*.a, as probably noone needs it
To the actual issue:
After deleting lib/*.a in f7d5210:
That doesn't look too bloated to me in comparison, and mysql55 isn't in default closures anyway (anymore).
It is bloated, because all the binaries are kind of statically linked. They are dynamic, but the build process include something static into them. The binaries are huge, while they could be much smaller.
I've tried to investigate but cmake burns my mind.
Hmm, it seems Debian has much smaller sizes.
At least, what is in most closures, libmysqld, is about similar size. Maybe some plugins or other stuff could be removed from the default closure, I don't know.
Is it relevant nowadays?
It's still bloated but excluded from most closures.