Bug #9779 mysqld_safe doesn't work correctly when rpm --relocate is used
Submitted: 9 Apr 2005 1:17 Modified: 4 May 2005 9:31
Reporter: Jorge del Conde Email Updates:
Status: Won't fix Impact on me:
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:4.1.11 - rpm OS:non win32
Assigned to: Lenz Grimmer CPU Architecture:Any

[9 Apr 2005 1:17] Jorge del Conde
in the rpm version of our distribution, mysqld_safe has several paths "hard-coded", and problems occure when installing the rpm with the --relocate option.  This causes arguments to mysqld_safe such as --basedir and --ledir not to function correctly.

How to repeat:
Replace hard-coded paths with variables that can be replaced in the parse_arguments() function.  For example 'MY_BASEDIR_VERSION'.
[4 May 2005 9:31] Lenz Grimmer
The way files our RPMs are currently organized does not allow relocation - too many paths are
hard-coded and the files are spread across various directories. We don't plan on changing the RPM
layout - please use a binary tarball if you need to install MySQL into a different location.