<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Rename "kde5" VCL" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125922#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Rename "kde5" VCL" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125922">bug 125922</a> from <a class="email" href="mailto:m.weghorn@posteo.de" title="Michael Weghorn <m.weghorn@posteo.de>"> Michael Weghorn</a> <pre>After thinking about it for a while, I'd currently prefer to stay with the name as is, if this is OK for everybody involved. While I do understand that "kde5" maybe wasn't the best choice for the naming, it'd rather be confusing to change it now. (In reply to Jan-Marek Glogowski from <a href="show_bug.cgi?id=125922#c6">comment #6</a>) > Just to make it more clear, my suggestion is to rename libvclplug_kde5lo.so > => libvclplug_kf5lo.so and display kde5 => kf5. But in case we rename it, I think it's better to rename it everywhere, since I think it would be rather counter-produtive wrt the intent mentioned in the initial report ("reduce confusion and improve consistency") to have it called "kde5" at some places and "kf5" at others. 'git blame' should be no problem, since 'git help blame' says: "The origin of lines is automatically followed across whole-file renames (currently there is no option to turn the rename-following off)." > > I hope gtk3_kde5 will fade out over time, so leave that as it. As probably will kde5 once qt6 takes over? :-) So maybe that would be a good point to start with a proper name just from the beginning?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>