MySQL Bugs: #12550: mysql.server script contains libexec=basedir/bin and other problems

Bug #12550	mysql.server script contains libexec=basedir/bin and other problems
Submitted:	12 Aug 2005 12:36	Modified:	14 Sep 2005 4:17
Reporter:	Gleb Paharenko	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Compiling	Severity:	S3 (Non-critical)
Version:	5.0.12	OS:	Linux (Linux)
Assigned to:	Jim Winstead	CPU Architecture:	Any

Description:
I've installed mysql-5.0.12 from Bk source tree. mysql.server script contains lines
libexecdir="$basedir/bin". Therefor  I'm unable to start server, because after building,
mysqlmanager are in libexec directory. My configure string:

  env CFLAGS="-O3 -mtune=pentium-m" CXX=gcc CXXFLAGS="-O3 -mtune=pentium-m -felide-cunstructors" ./configure --prefix=/var/lib/mysql5 --without-bdb --with-extra-charsets=complex --enable-local-infile --disable-shared --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static  --enable-thread-safe-client

Another thing, I've found - is that if I specify the basedir and datadir at the beginning of 
the file - it doesn't have any effect, because, mysql.server sript executes parse_server_arguments where it overwrites the values of previously specified variables (basedir and datadir).

How to repeat:
see description
I've downloaded my mysql.server to ftp.mysql.com/pub/mysql/uploads

Suggested fix:
Fix it or explain why the value of libexec is $basedir/bin, instead of $basedir/libexec

Specifying basedir in /var/lib/mysql5/my.cnf solves the problem, however, in my opinion,
if I've specified the basedir in mysql.server, i shouldn't specify it again in the configuration file

Thanks for your bug report.  Verified w/5x from bk

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/28904

Fixed in 5.0.13.

Documented in 5.0.13 changelog:

 <listitem><para>
       The <filename>mysql.server</filename> script contained incorrect path for the <literal>libexec</literal> directory. (Bug #12550)
      </para></listitem>