public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] LINGUAS handling
Date: Fri, 11 Jun 2010 08:58:29 +0400	[thread overview]
Message-ID: <1276232309.16507.554.camel@tablet> (raw)
In-Reply-To: <20100609192121.GA16981@boostbox>

В Срд, 09/06/2010 в 21:21 +0200, Harald van Dijk пишет:
> On Wed, Jun 09, 2010 at 11:38:03AM +0400, Peter Volkov wrote:
> > 1. Do we want all packages to support LINGUAS if possible? It is
> > possible to leave gettext based package without LINGUAS and everything
> > will just work, but I think that it's good idea to make supported
> > languages visible to user through linguas_<lang> flags.
> 
> I agree, but I'd like to point out this would be a visible change in
> default behaviour: the default would change from "install everything" to
> "install nothing". For gettext-based packages, "install everything" is a
> sane default, in my opinion.

Yup, but 1) this change will be visible during emerge -pv since new
linguas value are visible there, 2) we already have gettext packages
with linguas supported.

> > 2. How should we handle case of unset LINGUAS in ebuild? Should we mimic
> > gettext and install all supported languages, using code like
> > 
> > LINGUAS=${LINGUAS-%UNSET%}
> > if test "%UNSET%" == "$LINGUAS"; then
> > 	# install all supported languages
> > fi
> 
> Firstly, don't use == with test.

Thank you for suggestions! Actually it was just an illustration loosely
taken from bug 148702.

> Unfortunately, consistency either way is bad. Making unset LINGUAS
> install nothing changes gettext's design, when the whole idea behind
> LINGUAS was to mimic gettext's design. Making unset LINGUAS install
> everything causes massive disk space requirements for the default
> settings for some packages such as openoffice. In my opinion, either of
> those would be worse than having LINGUAS behave inconsistently.

Ok.

> > 3. What is the purpose of strip-linguas function
> 
> It's used for some packages that fail to build with certain LINGUAS
> values. If I recall correctly, binutils had a bug where putting en_GB in
> your LINGUAS made the build fail, for example. binutils doesn't support
> en_GB anyway, so it gets filtered out,

I see.

But what is preferred way for gettext packages? Define supported
languages in IUSE or use strip-linguas if required?

-- 
Peter.




      parent reply	other threads:[~2010-06-11  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09  7:38 [gentoo-dev] LINGUAS handling Peter Volkov
2010-06-09 19:21 ` Harald van Dijk
2010-06-09 22:08   ` [gentoo-dev] " Duncan
2010-06-11  4:58   ` Peter Volkov [this message]

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=1276232309.16507.554.camel@tablet \
    --to=pva@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