public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Harald van Dijk" <truedfx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] IUSE and LINGUAS?
Date: Mon, 30 Jan 2006 19:42:02 +0100	[thread overview]
Message-ID: <20060130184202.GA27875@gentoo.org> (raw)
In-Reply-To: <200601300617.36417@enterprise.flameeyes.is-a-geek.org>

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

On Mon, Jan 30, 2006 at 06:17:36AM +0100, Diego 'Flameeyes' Pettenò wrote:
> [ebuild   R   ] media-tv/kdetv-0.8.8-r1  USE="-arts -debug -lirc -opengl 
> -xinerama -zvbi" LINGUAS="it% -bg% -br% -ca% -cs% -cy% -da% -de% -el% -en_GB% 
> -es% -et% -fi% -fr% -ga% -gl% -hu% -is% -lt% -mt% -nb% -nl% -pa% -pl% -pt% 
> -pt_BR% -ro% -ru% -rw% -sr% -sr@Latn% -sv% -ta% -tr% -zh_CN%" 0 kB
>...
> the linguas_* useflags should be listed in use.desc (consider that it would 
> take a while, _if_ we decide to go this route, before all packages are 
> updated to do this, but it's silly to pollute the use.local.desc file until 5 

How would this work with packages which treat unset LINGUAS as "install
all languages", and empty but set LINGUAS as "install no languages" (the
way LINGUAS was supposed to work)? When changing between the two, emerge
-pv would show no changes, and there is no way for ebuilds to work
around that. I'm all for telling users what parts of a package are
optional, but incorrect info is worse than no info. (This doesn't apply
to the KDE ebuilds, since they treat empty and unset LINGUAS the same,
but you said all packages.)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2006-01-30 17:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-30  5:17 [gentoo-dev] IUSE and LINGUAS? Diego 'Flameeyes' Pettenò
2006-01-30  7:43 ` Ciaran McCreesh
2006-01-30 11:46   ` Jason Stubbs
2006-01-30 11:54     ` Ciaran McCreesh
2006-01-30 13:22       ` Diego 'Flameeyes' Pettenò
2006-01-31 11:31       ` Jason Stubbs
2006-01-31 11:50         ` Ciaran McCreesh
2006-01-31 13:39         ` Mike Frysinger
2006-02-01  0:55           ` Jason Stubbs
2006-02-01  1:08             ` Donnie Berkholz
2006-02-02 19:46             ` Diego 'Flameeyes' Pettenò
2006-02-02 19:55               ` Ciaran McCreesh
2006-02-05 14:51                 ` Diego 'Flameeyes' Pettenò
2006-02-05 20:34                   ` Mike Frysinger
2006-02-05 20:43                     ` Diego 'Flameeyes' Pettenò
2006-02-05 20:54                       ` Ciaran McCreesh
2006-02-05 21:04                       ` Mike Frysinger
2006-02-05 21:16                         ` Diego 'Flameeyes' Pettenò
2006-02-05 20:50                     ` Alec Warner
2006-02-05 16:31                 ` Diego 'Flameeyes' Pettenò
2006-01-30 12:31     ` Re[2]: " Jakub Moc
2006-01-30 13:20       ` Diego 'Flameeyes' Pettenò
2006-01-30 11:43 ` Jason Stubbs
2006-01-30 13:23   ` Diego 'Flameeyes' Pettenò
2006-01-30 16:15 ` Diego 'Flameeyes' Pettenò
2006-01-30 16:38   ` Mike Frysinger
2006-01-30 16:48     ` Diego 'Flameeyes' Pettenò
2006-01-30 18:03       ` Mike Frysinger
2006-01-30 17:00     ` [gentoo-dev] " Duncan
2006-01-30 18:42 ` Harald van Dijk [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=20060130184202.GA27875@gentoo.org \
    --to=truedfx@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