On Sun, 27 Jan 2019 at 04:52, Elliott Sales de Andrade <quantum.analyst@xxxxxxxxx> wrote:
[..]
I see three ways forward:
1. Teach %find_lang to add directories if it's not in /usr/share/locale
2. Tell packagers to explicitly include the directories is not in
/usr/share/locale
3. Stop recommending %find_lang if it serves no other purpose than to
just list files (I *think* multiple packages owning directories is no
longer an issue?)
I'd lean towards 1 as I think 2 is just unnecessary extra work and the
condition in 3 is not probably true.
4. Maintaining distribution is about introducing standards applied to all packages. Instead folowing crazy/incorrect things implemented in original source code add patch to fulfill distrinbution standards and submit it to source code maintainer (at least availaible as buid-time option).
Even in case of using both python2 and python3 modules both versions will be using exactly the same .mo files and there is no any rational reasons to place those files within python site tree.
Other class of simillar cases is related to many web applications especially written in php. Even in case of those packages it is possible to change php code to change web app behaviour to open .mo files installed in std %{_datadir}/locale.
find-lang.sh backend script should be modified/extended only to handle new the class lang dependent files (this is why I've added many years ago handle --with-gnome in this script). In your case we are talking about regular gettext .mo files only installed in non-std location.
Please follow the standards.
kloczek
--
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
