MySQL Bugs: #32786: MySQL adds unnecessary subdirectory /opt/mysql/mysql

Bug #32786	MySQL adds unnecessary subdirectory /opt/mysql/mysql
Submitted:	27 Nov 2007 19:14	Modified:	4 Mar 2013 11:52
Reporter:	Stian Oksavik	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S4 (Feature request)
Version:	5.0.45, 5.1RC	OS:	Solaris
Assigned to:		CPU Architecture:	Any

Description:
Instead of /opt/mysql, MySQL installs in /opt/mysql/mysql

This is merely cosmetic, but it seems redundant. This is probably due to a redundant path being added during the pkgproto or pkgmk stages of building the package.

How to repeat:
Install the package.

ls -ld /opt /opt/mysql

Suggested fix:
Install directly into /opt/mysql

Thank you for a problem report. I think your request to use just /opt/mysql is reasonable enough, but note that according to Filesystem Hierarchy Standard 2.3, http://www.pathname.com/fhs/pub/fhs-2.3.pdf:

"The structure of the directories below /opt/<provider> is left up to the packager of the software, though it is recommended that packages are installed in /opt/<provider>/<package> and follow a similar structure to the guidelines for /opt/package. A valid reason for diverging from this structure is for support packages which may have files installed in /opt/<provider>/lib or /opt/<provider>/bin."

So, if "mysql" is provider and "mysql" is a package, current structure is NOT against the standard. That is why I treat this as a (reasonable enough) feature request, but not a bug.

Valid arguments can indeed be made both ways. This means that we will not plan to change the current practice.