Am 02.05.24 um 9:33 PM schrieb Joe Salmeri:
On 5/2/24 3:26 PM, Andrei Borzenkov wrote:
On 02.05.2024 21:25, Joe Salmeri wrote:
So where is the configuration that you refer to that will stop it from installing the language packages ?
zypper removelocale en_US
Don't I want that since I'm in the United States ?
You said you didn't want any *-lang packages and in that case removing all locales should be the right thing to do. Some *-lang packages declare support for en_US, for example firewalld-lang provides locale(firewalld:en_US) via /usr/share/locale/en_US/LC_MESSAGES/firewalld.mo. I have no idea what happens if you remove firewalld-lang, and why a localization for en_US exists. Usually en_US is built in, but maybe not here, or maybe they've decided to duplicate it anyway. You can find all packages providing en_US/en locales like this: zypper search --provides 'locale(*:en_US)' zypper search --provides 'locale(*:en)' And maybe (see below): zypper search --provides 'locale(*:en_*)'
It isn't clear to me what the difference between the 2 reported by zypper lloc ?
Are you saying that 'en' and 'en_US' are really the same and that zypper is installing the languages because there is more than one code/language configured?
My understanding is that zypper automatically looks for providers of locale(X:L) for all installed packages X and all "requested" locales L. If a requested locale is not available, but the "fallback" locale is, that is selected instead. In your case, you get all locale(*:en_US) corresponding to packages that you have, plus all locale(*:en) for packages that you have that don't have a corresponding locale(*:en_US). Likely the fallback accepts any en_*, in which case you'd get the en_GB localization or whatever else might be there. That's what you want for small countries: a Swiss German (or German-speaking Swiss) would select de_CH as locale. They'd get de_CH for packages that have it, but there are probably not a lot of them. However, a Swiss German should still understand other German dialects, and so they get de_DE (German as written in Germany) as fallback that most packages should have. Same goes for all the Spanish-speaking countries, and so on. And a British user might also appreciate that their computer talks to them in British English and falls back to AE only if BE isn't available.
If so, maybe the install process needs to be updated so it doesn't do that ?
If en_US is guaranteed to always be built in, it should probably be excluded from locales. But I'm not sure if that's the case. Otherwise, packages should perhaps themselves provide locale(*:en_US) if they have localization and en_US built in. But that seems like a bit of work that someone would have to invest. ;) If nobody is willing to do that, you'll have to live with the *-lang packages or drop your en_US locale as Andrei suggested. Aaron