From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: l10n.eclass
Date: Fri, 20 Jul 2012 13:55:46 -0400 [thread overview]
Message-ID: <CAJ0EP41skuKWjmfQieJbnhj4qFAmaTGWBSBQOdN_C3XdfHVsDw@mail.gmail.com> (raw)
In-Reply-To: <20120720075457.4cccea26@googlemail.com>
On Fri, Jul 20, 2012 at 2:54 AM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> On Thu, 19 Jul 2012 18:34:41 -0400
> Mike Gilbert <floppym@gentoo.org> wrote:
>> On Thu, Jul 19, 2012 at 5:13 PM, Zac Medico <zmedico@gentoo.org>
>> wrote:
>> > On 07/19/2012 06:14 AM, Ralph Sennhauser wrote:
>> >> Could be that Portage re-exports a sanitized
>> >> LINGUAS tough, but I doubt it.
>> >
>> > Portage does sanitize it if there are any linguas_* flags in IUSE,
>> > otherwise it lets the variable pass through without sanitizing it.
>>
>> That's good; we definitely don't want to "sanitize" it if there are no
>> linuguas_* flags in IUSE. This would break LINUGUAS support for many
>> autotools/gettext based packages, where the autotools code parses
>> LINGUAS directly and the ebuild does nothing with it.
>
> If there aren't any linguas_* flags in IUSE, LINGUAS should be empty,
> and will be in future EAPIs. Without that, USE dependencies on
> USE_EXPAND variables don't work.
>
Do you mean that LINGUAS will be empty, or unset (undefined) in an
ebuild context? The difference is significant here.
next prev parent reply other threads:[~2012-07-20 17:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 6:45 [gentoo-dev] RFC: l10n.eclass Ben de Groot
2012-07-19 13:14 ` Ralph Sennhauser
2012-07-19 15:37 ` Ben de Groot
2012-07-20 7:33 ` Ralph Sennhauser
2012-07-23 12:29 ` Ben de Groot
2012-07-23 15:22 ` Ralph Sennhauser
2012-07-19 16:15 ` Ciaran McCreesh
2012-07-19 21:13 ` Zac Medico
2012-07-19 22:34 ` Mike Gilbert
2012-07-20 6:54 ` Ciaran McCreesh
2012-07-20 16:39 ` Mike Gilbert
2012-07-20 17:09 ` Ciaran McCreesh
2012-07-20 17:29 ` Mike Gilbert
2012-07-20 17:35 ` Ciaran McCreesh
2012-07-20 17:43 ` Alexandre Rostovtsev
2012-07-20 17:46 ` Alexandre Rostovtsev
2012-07-20 17:54 ` Ciaran McCreesh
2012-07-20 18:37 ` Alexandre Rostovtsev
2012-07-20 18:41 ` Ciaran McCreesh
2012-07-20 19:15 ` Alexandre Rostovtsev
2012-07-20 19:17 ` Ciaran McCreesh
2012-07-20 19:48 ` Alexandre Rostovtsev
2012-07-20 20:02 ` Ciaran McCreesh
2012-07-20 20:10 ` Alexandre Rostovtsev
2012-07-20 20:15 ` Ciaran McCreesh
2012-07-20 20:11 ` Ian Stakenvicius
2012-07-20 19:05 ` Ian Stakenvicius
2012-07-20 19:13 ` Ciaran McCreesh
2012-07-20 20:08 ` Ian Stakenvicius
2012-07-20 17:44 ` Michał Górny
2012-07-20 18:03 ` Alexandre Rostovtsev
2012-07-20 17:55 ` Mike Gilbert [this message]
2012-07-20 18:03 ` Ciaran McCreesh
2012-07-20 18:09 ` Mike Gilbert
2012-07-20 18:15 ` Ciaran McCreesh
2012-07-19 22:44 ` Mike Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ0EP41skuKWjmfQieJbnhj4qFAmaTGWBSBQOdN_C3XdfHVsDw@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox