| 1 |
There is a use variable "nls" which is supposed to be used exactly in such |
| 2 |
situation. Please also take a look at /usr/portage/profiles/use.desc for more |
| 3 |
use variables. |
| 4 |
you can use it in an ebuild for example like that: |
| 5 |
use nls && myconf="$myconf --with-whatever" |
| 6 |
and then use myconf to pass necessary flags to configure. You can grep throug |
| 7 |
ebuilds for more info. |
| 8 |
|
| 9 |
George |
| 10 |
|
| 11 |
On Thursday 09 May 2002 21:37, Einar Karttunen wrote: |
| 12 |
> Hello |
| 13 |
> |
| 14 |
> What is the official way of adding localisation support |
| 15 |
> to applications. One possible solution would be to |
| 16 |
> include use flags for the various localisations. |
| 17 |
> Take for example aterm which has optional support for |
| 18 |
> japanese (and?)/or chinese. Now the default aterm |
| 19 |
> ebuild should not build them by default (they make |
| 20 |
> displaying e.g. iso-8895-* difficult) and it would |
| 21 |
> be quite problematic to make many versions of the |
| 22 |
> same package for the different users. I want |
| 23 |
> to know what is the way chosen by gentoo to |
| 24 |
> handle this. |
| 25 |
> |
| 26 |
> - Einar Karttunen |
Archives