[debian-mysql] My issues with the structure of the mysql-5.5 package
Olaf van der Spek
ml at vdspek.org
Fri May 18 18:20:13 UTC 2012
On Fri, May 18, 2012 at 1:47 AM, Nicholas Bamber <nicholas at periapt.co.uk> wrote:
> innotop n/a [separate source anyway]
> replace n/a [would have to have separate docs directory]
That's a very generic package name. Shouldn't something less generic be used?
> mysql-common n/a
> mysql-source-5.5 mysql-common
> mysql-testsuite-core-5.5 mysql-common
> mysql-testsuite-5.5 mysql-testsuite-core-5.5
What's the difference between core and non-core?
> mysql-testsuite mysql-testsuite-5.5
> libmysqlclient18 mysql-common
> libmysqlclient-dev mysql-common
> libmysqld-dev libmysqlclient18
> libmysqld-pic libmysqlclient18
Why do these depend on client?
> mysql-client-core-5.5 mysql-common, libmysqlclient18 (via
> mysql-client-5.5 mysql-client-core-5.5
What's the diff between core and non-core?
More information about the pkg-mysql-maint