On Tue, 2005-09-27 at 15:07 +0200, Thomas de Grenier de Latour wrote: > On Tue, 27 Sep 2005 08:35:43 -0400 > Chris Gianelloni <[EMAIL PROTECTED]> wrote: > > > Unfortunately, even trying to add -linguas_fr to package.use, > > still results in the French language pack being installed over > > the English. > > This reminds me bug #104573: it was the same problem where some > LINGUAS="fr" users didn't want to have manpages-fr installed. The > workaround used there was to add the "nls" USE flag. This way you > separate the "do you want some translations?" question from the > "what translations do you want?" question.
Actually, I like this idea. It isn't perfect, but it allows one to add -nls for the package in package.use to turn off translations. It still doesn't completely solve the problem, however. The user in question has LINGUAS="en_US fr" but wants the English translation. This would be fine for this user, but what if the user had wanted the French translation and not English? > But sure, it's more a workaround than an ideal solution. > > > For one, things in USE_EXPAND would need to be negate-able in > > package.use. > > It may be a problem if an ebuild relies on the USE flags being > coherent with the env var itself. I don't have example of such > ebuilds in mind though, but i guess it could happen that, for > instance, on one hand the LINGUAS var is used by autotools to > choose the locales to install, and on the other hand the linguas_* > flags are used to add some help files or spell dicts: this could > result in some kind of half-translated apps, maybe even broken > apps, i don't know... I hadn't considered this situation, as I was stuck thinking of binary apps (nwn and civ-ctp). -- Chris Gianelloni Release Engineering - Strategic Lead Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
