[debian-mysql] My issues with the structure of the mysql-5.5 package

[Nicholas Bamber]

On 18/05/12 21:22, Olaf van der Spek wrote:
> On Fri, May 18, 2012 at 8:29 PM, Nicholas Bamber<nicholas at periapt.co.uk>  wrote:
>>>> replace                  n/a [would have to have separate docs directory]
>>>
>>>
>>> That's a very generic package name. Shouldn't something less generic be
>>> used?
>>
>>
>> You mean "replace".
>
> Yes
>
>> Please feel free to suggest a better one. Definitely not
>> "mysql-replace" as it really has nothing to do with MySQL.
>
> Does Debian have some guidelines for this?


http://www.debian.org/doc/debian-policy/ch-binary.html#s3.1

>
>>>
>>>> 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?
>>
>>
>> In this case core consists of all the binaries and non-core the test scripts
>> and result files.
>
> Are the testsuite binaries useful without the test scripts?

In principle yes. It is a sophisticated test suistem . In practice I 
doubt it is adequately documented.

>
>> In this case core is "mysql" and "mysqlcheck". And I made an error. It's
>> non-core that depends on libmysqlclient18 (via
>>>> libdbd-mysql-perl).
>
> I think listing the contents (instead of the dependencies) would be useful.
>


http://wiki.debian.org/Teams/MySQL/WhichPackage

I could add a proposed package column to that.