public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: l10n.eclass
Date: Fri, 20 Jul 2012 15:05:35 -0400	[thread overview]
Message-ID: <5009ABFF.4050100@gentoo.org> (raw)
In-Reply-To: <20120720185419.23244eb7@googlemail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 20/07/12 01:54 PM, Ciaran McCreesh wrote:
> On Fri, 20 Jul 2012 13:43:15 -0400 Alexandre Rostovtsev
> <tetromino@gentoo.org> wrote:
>>> If you dep upon foo[linguas_en(+)] and linguas_en isn't in
>>> IUSE, what happens?
>> 
>> Fatal error. If a package installs its translations implicitly
>> via gettext's rules depending on the value of LINGUAS at
>> configure time, then obviously other packages must rely on that
>> package having installed any particular translation.
> 
> Uh, the entire point of the (+) is that it's *not* a fatal error if
> you have a default.
> 

If this doesn't work (assuming foo provides whatever this package
needs it to have for linguas_en), then the dep is wrong in the first
place and either (+) shouldn't be set or the use-dep on foo shouldn't
exist to begin with.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlAJq/4ACgkQ2ugaI38ACPDIrgEAlPMn/3pSM/GK3BbCozQgGpxc
9aSnmtIXlOsr7HZ7QcUA/1dbtqqt6B/ClgriFHvHcVpZEiz5QiQh6RJ2t4Mr5jgk
=ai7O
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2012-07-20 19:06 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 [this message]
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
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=5009ABFF.4050100@gentoo.org \
    --to=axs@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