Daniel Campbell posted on Tue, 31 May 2016 10:31:22 -0700 as excerpted: > I think this idea has some potential, but would there be a way for a > user to choose L10N *or* INSTALL_MASK instead of both? If I understand > correctly, a person who wanted all of their system to be en_US only, but > wanted to take part in translation of some other project, would need to > add the other locales directly to L10N, then somehow mask them out for > other packages. Or the reverse: leave L10N="en_US" or something, and > somehow enable other languages in that specific package. > > Is there a package-level option for this? Users can set their locales in > /etc/locale.gen, and that handles things globally, but what about the > user that doesn't want to include that for all of their packages? This > seems like an all-or-nothing thing, lacking in granularity. If I'm > wrong, please clarify so I can understand better.
For portage at least, pretty much all vars, including the proposed L10N, can be set per-package using /etc/portage/package.env and the files it points to in /etc/portage/env/. (The package.env method works during the python phase as well, but is primarily for direct variable setting and isn't as flexible as the older /etc/portage/env/cat-egory/pkg/file method, which only works during the bash/ebuild phase, but exposes the full richness of bash to be used as it's actually bash executing it.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
