MySQL Bugs: #31989: InnoDB is contained in "cluster" RPMs

Bug #31989	InnoDB is contained in "cluster" RPMs
Submitted:	31 Oct 2007 14:59	Modified:	16 Nov 2007 13:20
Reporter:	Joerg Bruehe	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S3 (Non-critical)
Version:	5.0 before 5.0.50	OS:	Linux
Assigned to:	Joerg Bruehe	CPU Architecture:	Any

Description:
In RPM packages configured as "cluster" of versions before 5.0.50,
we erroneously included InnoDB.

(This happened by accident, because including InnoDB is the default action of "configure", so we need to explicitly specify "--without-innodb" if it is not to be included in the build.)

This does not affect "tar.gz" and derived packages: "depot", "dmg", "pkg".

This has now been fixed, the fix will be effective for 5.0.50 and up.

(5.1 is not affected, because we do not yet build "cluster" RPMs of that release family.)

How to repeat:
The build team knows that ...

Suggested fix:
Add explicit "--without-innodb" to the RPM "spec" files for the "cluster" configuration.

Thank you for your bug report. This issue has already been fixed in the latest released version of that product.

Documented fix in 5.0.50 changelog.

See bug #52945