Bug #74754 MySQL documentation does not install
Submitted: 9 Nov 2014 14:00 Modified: 9 Nov 2014 14:59
Reporter: Peter Laursen (Basic Quality Contributor) Email Updates:
Status: Verified Impact on me:
Category:MySQL for Windows: Installer Severity:S3 (Non-critical)
Version: OS:Windows (7/64)
Assigned to: Assigned Account CPU Architecture:Any

[9 Nov 2014 14:00] Peter Laursen
The "MySQL Installer" has an option to install the MySQL documentation (currently 5.6.21 version). However it does not *install' it only *copies*. And furthermore it does not copy to the folder where it claims to do on 64 bit systems (it copies to "\program files (x86) .. " and not"\program files ..")

How to repeat:
I will upload an image

Suggested fix:
1) *installing* would (as per Windows-standards) at least mean that shortcuts (desktop- and startmenu- shortcuts) should be created. Maybe even an additonal dialog could display for user where she decides what shortcuts to create (I write "she" because only women bother to RTFM! The rest of us just do mistakes :-) ).

2) Display the correct "installation" path in the Installer interface on 64 bit systems. To avoid the ambiguity of installation folders in 32 and 64 bit Windows it could be considered to have it in "\Program Data .." instead.

.. and further 

3) There are two .pdf files in "C:\Program Files (x86)\MySQL\MySQL Documentation" 5.6 named "refman-5.6-en.pdf" and "refman-5.6-en.a4.pdf". It would be nice to have "refman-5.6-en.pdf" renamed to "refman-5.6-en.letter.pdf" (or whatever page format it uses). It could save a few rainforest to help users not to print the wrong version!
[9 Nov 2014 14:01] Peter Laursen
The image promised

Attachment: nodocs.jpg (image/jpeg, text), 240.75 KiB.

[9 Nov 2014 14:12] Peter Laursen
.. and *furthermoremore*: I don't think it makes much sense to describe the "architecture" of the PDF documentation as "X64". There is not separate documentation for 32 bit and 64 bit servers. "N/A" (= 'does not apply') is commonly used in such cases.
[9 Nov 2014 14:59] MySQL Verification Team
Thank you for the bug report. Verified as described.