[oe] [RFC] locales

Holger Freyther freyther at gmx.net
Wed Jun 20 10:40:14 UTC 2007

Am 20.06.2007 um 12:14 schrieb Sergey Lapin:

> As for infrastructure, I see several questionable methods of  
> solving this:
> 1. each package RRECOMMENDS its locale packages for locales mentioned
> in local.conf variable, and additional ones, which are related.

This would open the PACKAGE_ARCH hell. _armebdeenengbjpkoru to get a  
built for ARM EB with DE, EN, EN_GB, JP, KO and RU locales

> 2. image RRECOMMENDS locale packages blindly for all normal packages
> for languages which are in a var mentioned in 1.

This will require too much space in most of the cases. I'm thinking  
here of non Glib based

> 3. all -locale packages generated during builds are written to some
> special lists, for each language. Then meta-packages are generated
> from these lists.

This could work but......

the fundamental question is what is OpenSUSE, Fedora, Ubuntu doing to  
select a language? E.g. in the case of Opie you want to have a  
language for Opie, in the case for GPE you want to have gettext files  
for the whole system and GPE. You don't want to install translations  
where you don't have the package installed but when you install the  
package you want to have the translations automatically installed.

I don't think this is in the scope of OE but in the scope of  
distributions working together with the environment (GPE, Opie) to  
find a proper solution. Everything to implement it is already there....


More information about the Openembedded-devel mailing list