The CUPS ebuild sets its own default LINGUAS (e.g. ca, cs, de, etc) contrary to expectation - if LINGUAS is not defined the appropriate settings are deduced from the locale or assumed to be none.
If I set LINGUAS="en" for example, then the ebuild will disable the above LINGUAS as expected but setting this has knock effects with other packages that had acted correctly before. If I set the USE flag "linguas_en" then the ebuild reverts to all its LINGUAS. The only way I can specifically control the LINGUAS used by cups is to disable them all in /etc/portage/package.use:
net-print/cups -linguas_de -linguas_ca -linguas_cs -linguas_es -linguas_fr -linguas_it -linguas_ja -linguas_ru
I would expect CUPS not to pull in all its LINGUAS by default if LINGUAS is not set.
This came to light because the ebuild removed LINGUAS="pt_BR" meaning I have had to re-emerge all cups builds for no reason of interest to me and many others I expect.
(In reply to Robert Sharp from comment #0)
> This came to light because the ebuild removed LINGUAS="pt_BR" meaning I have
> had to re-emerge all cups builds for no reason of interest to me and many
> others I expect.
You could avoid such re-emerge by using "emerge --update --changed-use"
instead of "emerge --update --newuse".