<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Enhancement request: Set default install folder under Windows to \LibreOffice\" href="https://bugs.documentfoundation.org/show_bug.cgi?id=62303#c27">Comment # 27</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - Enhancement request: Set default install folder under Windows to \LibreOffice\" href="https://bugs.documentfoundation.org/show_bug.cgi?id=62303">bug 62303</a> from <a class="email" href="mailto:BridgeportContractor@gmail.com" title="Howard Johnson <BridgeportContractor@gmail.com>"> Howard Johnson</a> <pre>:-( On linux at least it seems this change has the consequence of having to now manually move user settings, extensions, and macro libraries to the new version 6, a non-trivial task. As near as I can tell from version 5 to 6 there are no changes required in the user settings, extensions, or macro libraries. Ref: <a href="https://ask.libreoffice.org/en/question/141322/when-upgrading-to-lo-60-whats-the-best-way-to-migrate-the-my-macros-standard-library/">https://ask.libreoffice.org/en/question/141322/when-upgrading-to-lo-60-whats-the-best-way-to-migrate-the-my-macros-standard-library/</a> But that notwithstanding, I think there should be: a) A multi platform installer for LO (instead of by different methods on different systems), and b) That installer should be able to migrate user content when upgrading if appropriate. Possibly it could even automatically modify or a least flag needed changes from version to version.\ I find it frustrating to see an issue on Windows be fixed, only to make a new problem for Linux.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>