Bug #59160 packages - src suffix used in an incoherent way
Submitted: 24 Dec 2010 16:29 Modified: 24 Dec 2010 19:04
Reporter: Santo Leto Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Packaging Severity:S3 (Non-critical)
Version: OS:Microsoft Windows
Assigned to: CPU Architecture:Any
Tags: inconsistency, intuitiveness, packages, SOURCE, src, usability
Triage: Triaged: D4 (Minor)

[24 Dec 2010 16:29] Santo Leto
Description:
Some source packages have the "src" suffix, some others no.

For example:

- connector net has: mysql-connector-net-6.3.5-src.zip						
- connector C++ has not: mysql-connector-c++-1.1.0.zip, mysql-connector-c++-1.1.0.tar.gz
- connector C has not: mysql-connector-c-6.0.2.tar.gz		
- odbc connector has not: mysql-connector-odbc-5.1.8.tar.gz		

- workbench has: mysql-workbench-gpl-5.2.31a-src.tar.gz, mysql-workbench-gpl-5.2.31a-src.zip

- the server has not: mysql-5.5.8-win32.zip, mysql-5.5.8.tar.gz, 		
- the cluster has not: mysql-cluster-gpl-7.1.9a.zip, mysql-cluster-gpl-7.1.9a.tar.gz		

- the proxy has not: mysql-proxy-0.8.1.tar.gz

Is there a logic behind these differences in package naming?

How to repeat:
Download packages.

Suggested fix:
Increase coherence and intuitiveness by adding src suffix when appropriate.
[24 Dec 2010 19:04] Valeriy Kravchuk
Thank you for the problem report.
[17 Jan 2011 13:20] Jonathan Perkin
Logic, no, this is just because all of these products are produced by different teams who all have their own ideas on how files should be named.

We are aiming to come to some kind of agreement over file naming schemes, but I'd say we're a long way off from seeing this implemented.