MySQL Bugs: #43260: Wrong name (version number part) generated for cluster (CGE) packages

Bug #43260	Wrong name (version number part) generated for cluster (CGE) packages
Submitted:	27 Feb 2009 13:03	Modified:	8 Jun 2009 20:00
Reporter:	Joerg Bruehe	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S2 (Serious)
Version:	Cluster 6.2 and up	OS:	Any
Assigned to:	Joerg Bruehe	CPU Architecture:	Any

Description:
Cluster (CGE) sources use a version scheme that contains both
- the version of the general server they are based on, and 
- the specific version of the cluster code.

This leads to versions like "5.1.32-ndb-6.3.23" which are confusing.

Cluster packages should get only the cluster version number into the package file name, like "6.3.23", as there are no two builds of cluster-6.3.23 using different versions of the general server.

The tool fix to ensure this is not yet present in the sources.

How to repeat:
Do a cluster build.

Suggested fix:
This fix was used in previous builds, but needs to get into the main sources.

--- old/scripts/make_binary_distribution.sh 2008-12-02 17:30:18.000000000 +0100
+++ new/scripts/make_binary_distribution.sh 2008-12-04 13:22:46.000000000 +0100
@@ -113,7 +113,12 @@
 esac

 # Change the distribution to a long descriptive name
-NEW_NAME=mysql@MYSQL_SERVER_SUFFIX@-@VERSION@-$PLATFORM$SUFFIX
+# For the cluster product, concentrate on the second part
+VERSION_NAME=@VERSION@
+case $VERSION_NAME in
+  *-ndb-* )  VERSION_NAME=`echo $VERSION_NAME | sed -e 's/[.0-9]*-ndb-//'` ;;
+esac
+NEW_NAME=mysql@MYSQL_SERVER_SUFFIX@-$VERSION_NAME-$PLATFORM$SUFFIX

 # ----------------------------------------------------------------------
 # Define BASE, and remove the old BASE directory if any

The necessary script change was committed on 2009-03-31,
and that was pushed to main 5.1 between 2009-05-08 and 2009-05-13.

Sadly, the commit did not mention this bug number, so progress on this matter was not recognized by the tools. My fault, sorry.

No need to document this IMO, as it does not affect users.
(This is a build tool we use internally.)

No changelog entry needed.