Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-devhelp
Navigation:
Lists: gentoo-devhelp: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-devhelp@g.o
From: Nikos Chantziaras <realnc@...>
Subject: Re: LINGUAS vs LANGUAGES
Date: Fri, 31 Jul 2009 18:26:45 +0300
On 07/21/2009 01:13 PM, Steven J Long wrote:
> Nikos Chantziaras wrote:
>
>> Thanks.  I ended up doing it this way, though with only one loop in
>> src_install(), which seems to be a bit more efficient and shorter:
>>
>>
>> LANGUAGES="de"
>> for i in ${LANGUAGES}; do
>> IUSE="${IUSE} linguas_${i}"
>> done
>>
> Just on a side-note (not saying it's how you want to do this one), this is
> something that BASH arrays are nice for (saving another loop):
> $ foo=(bar baz quux)
> $ echo "prefixed: '${foo[*]/#/pfx_}'"
> prefixed: 'pfx_bar pfx_baz pfx_quux'
>
> Parameter Expansion (incl on arrays) is discussed more at:
> http://mywiki.wooledge.org/BashFAQ/073

(Late reply because I was away on vacation.)

I ended up removing LINGUAS support altogether and installing the extra 
language file regardless of the user's LINGUAS.  The Gentoo developer 
maintaining the ebuild said that's how it should be done when the 
package only supports two languages.



References:
Re: LINGUAS vs LANGUAGES
-- Nikos Chantziaras
Re: LINGUAS vs LANGUAGES
-- Daniel Pielmeier
Re: LINGUAS vs LANGUAGES
-- Daniel Pielmeier
Re: LINGUAS vs LANGUAGES
-- Nikos Chantziaras
Re: LINGUAS vs LANGUAGES
-- Steven J Long
Navigation:
Lists: gentoo-devhelp: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: Re: LINGUAS vs LANGUAGES
Next by thread:
ebuild environment
Previous by date:
Re: Re: LINGUAS vs LANGUAGES
Next by date:
Re: Re: LINGUAS vs LANGUAGES


Updated Jun 03, 2012

Summary: Archive of the gentoo-devhelp mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.