public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
Subject: Re: [gentoo-dev] IUSE and LINGUAS?
Date: Mon, 30 Jan 2006 11:38:35 -0500	[thread overview]
Message-ID: <200601301138.35803.vapier@gentoo.org> (raw)
In-Reply-To: <200601301715.48101@enterprise.flameeyes.is-a-geek.org>

On Monday 30 January 2006 11:15, Diego 'Flameeyes' Pettenò wrote:
> On Monday 30 January 2006 06:17, Diego 'Flameeyes' Pettenò wrote:
> > Defining LINGUAS variable would be useful to allow people to know whether
> > they are going to have special support for their language in a package,
> > but it would also clutter the output quite a bit.
>
> Okay then.. I'm still looking locally how it appears, and I'm thinking it's
> really useful to have LINGUAS told in emerge -pv and -av.

it makes a the -pv output unreadable and thus useless ... although if you do 
something like -pvv, then the user can expect to get a lot of output ...

of course this still doesnt address the pita maintenance issue

> If somebody has a list of those variables, I would add them, it seems to me
> the most sensible way to do that, it would add documentation allowing
> people to know what they are going to do. Also, as use.desc is
> alphabetically sorted, all the linguas_* variables will stay together.

no, we have lang.desc already, dont clutter use.desc with this crap
-mike

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-01-30 16:40 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 [this message]
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 ` [gentoo-dev] " Harald van Dijk

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=200601301138.35803.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=flameeyes@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