%find_lang for non-standard locations

[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

[Tomasz Kłoczko]

On Sun, 27 Jan 2019 at 04:52, Elliott Sales de Andrade <
quantum.analyst(a)gmail.com&gt; 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

[Miro Hrončok]

On 27. 01. 19 4:42, Elliott Sales de Andrade wrote:
>  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?)
>   
4. use %find_lang and also own the entire dir in site-packages.

See 
https://src.fedoraproject.org/rpms/python2-django1.11/blob/master/f/pytho...



-- 
Miro Hrončok
--
Phone: [phone]
IRC: mhroncok