%find_lang for non-standard locations
by Elliott Sales de Andrade
Hi,
The general guidelines currently state that translations should be
found using %find_lang; this macro provides a listing of all *.mo
files but not their containing directories.
Specifying just the files makes sense when they are in the global
location (/usr/share/locale), but not so much when they are in, e.g.,
the Python site-packages directories. For example, python3-humanize
currently lists:
/usr/lib/python3.7/site-packages/humanize
...
/usr/lib/python3.7/site-packages/humanize/locale/fr_FR/LC_MESSAGES/humanize.mo
/usr/lib/python3.7/site-packages/humanize/locale/ko_KR/LC_MESSAGES/humanize.mo
/usr/lib/python3.7/site-packages/humanize/locale/ru_RU/LC_MESSAGES/humanize.mo
but *not* the humanize/locale or humanize/locale/* directories. So
when you uninstall python3-humanize, you are left with the
/usr/lib/python3.7/site-packages/humanize/locale/*/LC_MESSAGES/
directories.
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.
--
Elliott
