installation of mediatomb installs mysql-common

Bug #267833 reported by Brian Murray
2
Affects Status Importance Assigned to Milestone
mediatomb (Debian)
New
Undecided
Unassigned
mediatomb (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: mediatomb

The default configuration of mediatomb is to use a sqlite backend, however mysql-common ends up getting installed which seems excessive to me.

mediatomb-common depends on libmysqlclient15off which then depends on mysql-common.

Perhaps changing libmysqlclient15off to a suggests would resolve this issue.

I noticed this using mediatomb version 0.11.0-3 in Intrepid.

Revision history for this message
James Henstridge (jamesh) wrote :

The mediatomb binary is linked against libmysqlclient so that it can be used with a mysql backend. If the library is missing, then the program will not start. So simply suggesting the package is insufficient.

Removing the dependency would mean that the package couldn't be configured to run against MySQL. This would be a problem for people who are currently using that backend.

Revision history for this message
Leonhard Wimmer (leo-mediatomb) wrote :

James is right.

If the mysql dependency is removed, the mediatomb package would need a rebuild to be used with mysql.

The only option to get rid of the mysql library as hard dependency would be to change the upstream mediatomb code to use dlopen(3).

greets

Revision history for this message
Koen (koen-beek) wrote :

Maybe Ubuntu should have two mediatomb packages

mediatomb-lite without mysql support &
mediatomb with mysql support

or
mediatomb without mysql support &
mediatomb-mysql with mysql support

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.