public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: l10n.eclass
Date: Fri, 20 Jul 2012 14:03:09 -0400	[thread overview]
Message-ID: <1342807389.9434.33.camel@rook> (raw)
In-Reply-To: <20120720194426.1b01e9a1@pomiocik.lan>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

On Fri, 2012-07-20 at 19:44 +0200, Michał Górny wrote:
> On Fri, 20 Jul 2012 12:39:21 -0400
> Mike Gilbert <floppym@gentoo.org> wrote:
> 
> > For most gettext packages, there is absolutely no reason that the
> > ebuild maintainer should have to keep track of every translation
> > available in a given package across version bumps. If you change this
> > behavior in a future EAPI, you will break this.
>  
> Either he has to do that, or he should just remove the pointless,
> useless and unmaintained LINGUAS from his ebuild and just install
> everything.

Currently, "install everything" is treated as a bug - see
https://bugs.gentoo.org/show_bug.cgi?id=405485

If you ignore LINGUAS and install everything, you break the
long-established convention for what LINGUAS does, make users angry,
waste disk space, and increase build time for packages with lots of
translations - all for no good reason other than forcing uniform
USE_EXPAND conventions in a place where they aren't wanted.

-Alexandre.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2012-07-20 18:05 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 [this message]
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=1342807389.9434.33.camel@rook \
    --to=tetromino@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