While merging new version of glibc, the locale-archive file automaticaly replaced with new version. All user-defined locales (like my 'ru_RU.cp1251'), which not default, destroyed. It's not a big problem to run localedef again, but, maybe, showing warning after emerging, somthing like: "Check your locale settings" will be a good idea. And, if I do 'emerge -u world', and glibc one of updated packages, all packages after glibc will be build with incorrect locale settings (non-existent locale). I think, this not problem for many packages, but some gnome parts produce tons of warnings in this case (not sure about some missfunctionality in this packages after building with incorrect locale). P.S. Sorry for my english :) Reproducible: Always Steps to Reproduce: 1. 2. 3.
Could we please get somebody who knows a bit more than squid about locales to help out here ? =) I do not think it will be a good idea to add /usr/lib/locale/ to PACKAGE_MASK, locale-archive is binary anyhow.
This condition not very often anyway. It's specific for languages with many encodings, like russian (hehe, 6 or 7 different encodings for 33 letters in language :)). Maybe, just add at the end of ebuild the simple test (something like locale -a | grep $LANG). If test passed (current locale exists after emerge), continue normally. If test failed, pause emerge as after upgrading portage, and ask user for correct locale definition or LANG settings?
How exactly does it hurt if packages are compiled with a nonexistant locale set? And imho people who do localedef themselves have to remember to recreate the locale after a glibc update themselves :)
closing
