https://bugzilla.redhat.com/show_bug.cgi?id=156477
--- Comment #47 from Edgar Hoch edgar.hoch@ims.uni-stuttgart.de --- (In reply to Carlos O'Donell from comment #45)
(In reply to Panu Matilainen from comment #44)
Um, one should *never* modify /usr/lib/rpm/macros, that's a "factory config" setting and any changes will be overwritten on rpm upgrades. Local settings go into /etc/rpm files.
Agreed. Which is why I asked Edgar Hoch to file a new bug for rpm if it wasn't already solvable. I expect it is simply by setting the macros in /etc/rpm.
I was thinking about the problem. I came to the result that if a package is installed the files in /usr/... should be always the same for the same package, on every system. The locale data file is not a configuration file, it is a data file. Data files should not change while they are installed.
I would never expect that I have to reinstall a package if I would need more locales (languages). It should be predefined what a package provides and what not.
I think a reasonable solution would be to provide only the minimum of locales with the basic glibc package and to create additional (dependent) packages for each locale (as the exist for other packages, for example libreoffice, aspell, etc.). This language packages can be handled in the usual way by yum, dnf, etc.
So I think the rpm *install script should not call build-locale-archive, but locale-archive should only contain the minimum locales and glibc should search for other locales in other language dependent locale files.