Bernie Innocenti wrote: > On Thu, 2010-02-11 at 06:16 -0800, Carlo Falciola wrote: >> Is it available an (end -user easy) procedure to add language packs been >> stripped? >> I see a use case for teacher/volunteers/etc. that could need to have a >> different language available even "after" deployement... > > I think what matters from the user's PoV is activity translations, not > base OS translations.
That makes some sense... > For the system RPMs, I'd actually recommend scrapping all languages but > en_US.UTF-8 (which is usually the "internal" language of command line > tools, so it doesn't add any external catalog files). > > The Sugar packages need to be installed with all languages, though. This > might be tricky to do because yum installs those in a single > transaction, alongside the rest of the system. We could use the --instLangs parameter, indeed. However, this nukes all locales of a language... we used that in the early days when I started doing SoaS composes, but stopped at some point before the Strawberry release to make sure not to exclude anything. Generally, help with slimming the current image (so the nightlies) would be really appreciated. I gotta look into that at some point, too. --Sebastian _______________________________________________ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
