Description of problem:
When the install is done with a certain set of supported languages, this set is
only saved in /etc/sysconfig/i18n (env var "SUPPORTED"), but not used in
subsequent rpm operations, so any rpm operation (upgrade/install packages) will
install all languages.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RHEL4 U1 with a selected set of supported languages.
2. After installation, install/upgrade an rpm package with different language files
3. Now all language files of the installed/upgraded rpm's appear to be
installed, also for the not supported languages
Let Anaconda write a file /etc/rpm/macros.lang at installation time with the
correct language set, e.g.
This seems to work fine.
This is intentional. If you set %_install_langs, then there is no reasonable
way to add support for a new language after installation.
Can you explain?
At this moment you can not add support for a new language either, as the
installed files for the existing packages won't change (and this will never
change, I guess).
Now it's inconsistent: at install only the chosen subset is installed, after
that all languages are installed.
In my proposal at least all packages are installed the same way: during and
And "adding a supported language" afterwards would mean changing SUPPORTED in
/etc/sysconfig/i18n and %_install_langs in /etc/rpm/macros.lang. This will not
have effect on the installed packages, but that's the same as it is now.
We don't set %_install_langs in the install anymore either. Take a look in
anaconda/language.py and you'll see all the references to %_install_langs are
If we were still setting %_install_langs, then yes, this would make all kinds of
sense to do.
Hmmm... yes, I missed that, sorry for the confusion.
So, having language-specific files in an rpm is more-or-less useless, as only
complete rpm's are skipped via the language tags in comps.xml, right?