How to install library translations as libkfoo-<ABI-major>.mo instead of libkfoo.mo

[Chusslove Illich]

>> [: Stephan Kulow :]
>> And to spell it out: you can use -DLOCALE_INSTALL_DIR to KDE4, so KDE4
>> will install its locale files somewhere else - e.g. /usr/share/kde4/
>> locale. [...]

> [: Thiago Macieira :]
> What if we made that the default? That was part of my original proposal:
> all files that clash must carry a version number somewhere, either in the
> file name or in the path. By addign "kde4" to the path, you version the
> files.

Thinking more about this, I'm not sure that it is a good solution to split
KDE4 catalogs into another directory. If two packages are supposed to live
side by side on the system, the gettext-y way is that they install their
catalogs in standard locale dir, with different names. This is the expected
behavior, that won't surprise distributions.

Furthermore, if KDE4 kdelibs would install its catalogs and setup catalog
lookup into a special directory, then all KDE4 apps would follow the suite,
creating a parallel locale directory for the lifetime of KDE4.

So... While KDE3 and KDE4 libs should be installable side by side, how about
different versions of KDE4 libs? If not, as it seems reasonable to me, then
why not just rename those ~20 POTs in kdelibs to *4 scheme right now, mass
rename the existing POs in l10n-kde4, and be done with it?

-- 
Chusslove Illich (Часлав Илић)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070615/ef6855dd/attachment.sig>