#79 %find_lang for packages that do not store their lang files in /usr/share/locale
Closed: Invalid None Opened 12 years ago by tibbs.

The guidelines currently require the use of %find_lang for packages that contain locale files. However, this appears to significantly complicate the situation for packages which include locale files but don't store them in /usr/share/locale. For example, django has large numbers of translations separated out by application (in the django sense of application). Does it need to use %find_lang, or even do %lang tagging on those files? Doing so incredibly complicates the %files list to the point where the packager tries to autogenerate some of it, but still ends up with an incredible number of "file listed twice" errors.

Can we limit the requirement for %find_lang usage to packages which store their locale files in the regular place? Or is there a better way to handle this?


Please update this ticket regarding its continued relevance, providing any information requested. If this is not done within the next two weeks, this ticket may be closed due to inactivity. Thank you!

This ticket is being closed due to inactivity. If the issue referenced has
not been resolved, please reopen the ticket and provide the information
requested. Thank you!

Login to comment on this ticket.

Metadata