Dear Ludwig, sorry to reply to such an old thread, but facing an issue, that relates.. Am Montag, 24. Februar 2020, 10:13:40 CEST schrieb Ludwig Nussel:
Differnent topic and partially and solved via %lang_package macro already:
15.1: $ rpm -q --recommends bash bash-doc = 4.4 bash-lang = 4.4 $ rpm -q --supplements bash-lang bash
TW: $ rpm -q --supplements bash-lang $ rpm -q --recommends bash $ rpm -q --provides bash-lang bash-lang = 5.0.11-3.2 bash-lang-all = 5.0.11 locale(bash:bg) locale(bash:ca) locale(bash:cs) [...]
IOW bash-lang only gets pulled in when the system is set to one of the provided locales. Not sure if it works 100% with bash-lang though. It has files for that weird en@quot and en@boldquot locale.
I stumbled across a case, where this doesn't work as advertised:
Current Blender for TW uses a plain %lang_package, but:
$ rpm -q --provides blender-lang
blender-lang = 2.83.2-361.1
blender-lang-all = 2.83.2
This is from my build at home:frispete:blender but it's similar to graphics/
blender and what is in Factory.
Blender packages the translation file in a non-standard directory:
$ rpm -ql --provides blender-lang | grep -E '\