public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Improved ebuild information
Date: Sun, 02 Oct 2005 02:06:02 -0400	[thread overview]
Message-ID: <1128233162.10387.1.camel@vertigo.twi-31o2.org> (raw)
In-Reply-To: <433F2593.1070207@stiefelweb.de>

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

On Sun, 2005-10-02 at 02:10 +0200, Daniel Stiefelmaier wrote:
> >We've discussed adding this to metadata.xml a few times in the past,
> >but every time there was opposition from a vocal minority of one who
> >claimed that USE flags should always do exactly the same thing for
> >every package.
> >  
> >
> why do minorities rule?
> Actually i agree that in general use flags should have a consistent meaning.
> But anyway, if "perl" adds support for perl, the user might want to know 
> what it is good for in this package. or "plugins" could list the plugins 
> that would be added.
> 
> What tool ever would display the use flags description, it could use 
> those from
> /usr/portage/profiles/use.desc by default, which may be overwriten in 
> metadata.xml

Well, I think that it may be easier to simply add this information to
use.local.desc, as it already defines local USE flags.  The idea would
be that use.local.desc overrides use.desc when there is a conflict.
Then portage could, via a flag, show the use descriptions for each USE
flag per package.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

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

  reply	other threads:[~2011-10-31  3:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-01 20:19 [gentoo-dev] Improved ebuild information Daniel Stiefelmaier
2005-10-01 20:22 ` Ciaran McCreesh
2005-10-02  0:10   ` Daniel Stiefelmaier
2005-10-02  6:06     ` Chris Gianelloni [this message]
2005-10-05 18:03   ` Martin Schlemmer
2005-10-05 18:34     ` Ciaran McCreesh
2005-10-05 21:13     ` [gentoo-dev] " R Hill
2005-10-10 12:53       ` Chris Gianelloni
2005-10-10 17:36         ` Bruno
2005-10-10 19:02           ` Apreche
2005-10-10 19:23         ` R Hill
2005-10-10 19:56           ` Thomas de Grenier de Latour
2005-10-01 20:25 ` [gentoo-dev] " Simon Stelling
2005-10-02  0:46   ` Daniel Stiefelmaier
2005-10-02  2:35     ` Alec Warner

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=1128233162.10387.1.camel@vertigo.twi-31o2.org \
    --to=wolf31o2@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