kossebau added a comment.
In D29299#660519 <https://phabricator.kde.org/D29299#660519>, @pino wrote: > In D29299#660505 <https://phabricator.kde.org/D29299#660505>, @kossebau wrote: > > > Because people do strange things, and I prefer to rather not break their card house unless necessary. > > > Again, in which cases? The only way it might change the path is: use ki18n AND build with cmake AND use the ki18n_install macro AND define a KDE_INSTALL_LOCALEDIR variable yourself. Too many factors to make it even something to even bother thinking about TBH. Mileages difer :) One does not need to define KDE_INSTALL_LOCALEDIR oneself. One only needs to use find_package(KF5Plasma) or find_package(KF5Package), because some subrepo also does a plasma applet for Plasma integration or have someone cluelessly copied cmake code together because ENOTIMEFORBUILDSYSTEM and copying from the best=KDE and now-it-builds-so-do-not-touch-again. I have seen quite some cmake code, otherwise I would not be so passive here in the change (and yes, there is a world outside kde repos) :) And when you recommneded ki18n outside of kde spheres over the sad Qt i18n stuff, you do not want to see things falling apart, You yourself might not bother, but I do, because I have been hit myself too often in my life by people carelessly changing default things in minor releases, because worksformecanotimaginesomethingstrangewhybother. TBH I would not bother thinking about possibly breaking things for people, but just play safe. There is KF6 upcoming to change things. Why stop people caring for doing things more safely? :) REPOSITORY R249 KI18n REVISION DETAIL https://phabricator.kde.org/D29299 To: kossebau, ilic, heikobecker, #frameworks, aacid, ltoscano Cc: pino, kde-frameworks-devel, LeGast00n, cblack, michaelh, ngraham, bruns
