Bug #35105 | mysql_install_db refers to incorrect script locations on Windows | ||
---|---|---|---|
Submitted: | 6 Mar 2008 12:49 | Modified: | 15 May 2013 21:49 |
Reporter: | Philip Stoev | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Packaging | Severity: | S3 (Non-critical) |
Version: | 5.0.58 | OS: | Windows |
Assigned to: | Kent Boortz | CPU Architecture: | Any |
[6 Mar 2008 12:49]
Philip Stoev
[19 Mar 2008 11:19]
Philip Stoev
This bug is a property of our windows packages, not a property of the code or the BitKeeper tree. mysql_install_db.pl is generated from mysql_install_db.pl.in, and during that generation process, which appears to take place on the build machine, the hard-coded paths are placed into the script. Unfortunately, even if those hard coded paths are correct for UNIX (which has a unified directory structure), they will not appply for Windows, where both the drive and the program files directory are configurable. If we are unable to determine the correct installation path so that this script provides the correct output for the client system, then we should at least make a note that c:\program files is just an example and varies by system.
[11 May 2008 3:32]
MySQL Verification Team
Thank you for the bug report.
[29 Sep 2010 11:15]
Jonathan Perkin
We should probably just remove mysql_install_db.pl, Kent?
[26 Nov 2012 17:17]
gull faraz
nice work i like it http://www.readenews.com/2012/11/instagram-launches-profile-badges.html
[15 May 2013 21:49]
Yngve Svendsen
Obsolete Server version, and mysql_install_db is not supported on Windows and scheduled for removal from our Windows packages.