| 1 |
On Thu, 19 Jul 2012 18:34:41 -0400 |
| 2 |
Mike Gilbert <floppym@g.o> wrote: |
| 3 |
> On Thu, Jul 19, 2012 at 5:13 PM, Zac Medico <zmedico@g.o> |
| 4 |
> wrote: |
| 5 |
> > On 07/19/2012 06:14 AM, Ralph Sennhauser wrote: |
| 6 |
> >> Could be that Portage re-exports a sanitized |
| 7 |
> >> LINGUAS tough, but I doubt it. |
| 8 |
> > |
| 9 |
> > Portage does sanitize it if there are any linguas_* flags in IUSE, |
| 10 |
> > otherwise it lets the variable pass through without sanitizing it. |
| 11 |
> |
| 12 |
> That's good; we definitely don't want to "sanitize" it if there are no |
| 13 |
> linuguas_* flags in IUSE. This would break LINUGUAS support for many |
| 14 |
> autotools/gettext based packages, where the autotools code parses |
| 15 |
> LINGUAS directly and the ebuild does nothing with it. |
| 16 |
|
| 17 |
If there aren't any linguas_* flags in IUSE, LINGUAS should be empty, |
| 18 |
and will be in future EAPIs. Without that, USE dependencies on |
| 19 |
USE_EXPAND variables don't work. |
| 20 |
|
| 21 |
-- |
| 22 |
Ciaran McCreesh |
Archives