public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] IUSE and LINGUAS?
Date: Tue, 31 Jan 2006 20:31:55 +0900	[thread overview]
Message-ID: <200601312031.55860.jstubbs@gentoo.org> (raw)
In-Reply-To: <20060130115432.04dec824@snowdrop.home>

On Monday 30 January 2006 20:54, Ciaran McCreesh wrote:
> On Mon, 30 Jan 2006 20:46:28 +0900 Jason Stubbs <jstubbs@gentoo.org>
> wrote:
> | On Monday 30 January 2006 16:43, Ciaran McCreesh wrote:
> | > On Mon, 30 Jan 2006 06:17:36 +0100 "Diego 'Flameeyes' Pettenò"
> | > <flameeyes@gentoo.org> wrote:
> | > | Also, as repoman complain about linguas_blabla not being a valid
> | > | useflags, all the linguas_* useflags should be listed in use.desc
> | > 
> | > No, part of the point of USE_EXPAND is that they shouldn't. This is
> | > a repoman bug.
> | 
> | I have yet to be enlightened on any merit of USE_EXPAND is so perhaps
> | you could explain as to why there should be
> | user-configured-yet-undocumented options for ebuilds? More precisely,
> | how should they be documented if not via use.desc?
> 
> 1. Because for things like LINGUAS, there are arbitrarily many legal
> values, and documenting them all and keeping the list up to date would
> be extremely difficult.

"More precisely, how should they be documented if not via use.desc?"

> 2. Because USE_EXPAND is used for special USE things like arch and
> userland, and because we undocumented the special arch USE flags
> because they're not user settable.

These variables are internal and not meant to be user configurable.

--
Jason Stubbs

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-01-31 11:37 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 [this message]
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 ` [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=200601312031.55860.jstubbs@gentoo.org \
    --to=jstubbs@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