public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tuan Van <langthang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New global USE flag: examples
Date: Mon, 23 Aug 2004 07:34:53 -0700	[thread overview]
Message-ID: <412A008D.7010802@gentoo.org> (raw)
In-Reply-To: <200408231423.29976.pauldv@gentoo.org>

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

Paul de Vrieze wrote:

>On Saturday 21 August 2004 21:52, Ciaran McCreesh wrote:
>  
>
>>On Sat, 21 Aug 2004 16:46:15 -0300 Norberto Bensa
>>
>><norberto+gentoo-dev@bensa.ath.cx> wrote:
>>| And when you go to use.local.desc all you see is:
>>|
>>|  cat/package:flag1 - enables flag1 compilation/support
>>|
>>| It doesn't say what flag1 is good for! So you end up Googleing,
>>| etc...
>>
>>You might want to file bugs for these... Updating use{,.local}.desc
>>doesn't take particularly long, and a good description can save users a
>>lot of time.
>>    
>>
>
>The problem is that many "even official global useflags" would sometimes 
>require package-level descriptions on their effect. Maybe this should be 
>put in the ebuild itself.
>
>Paul
>
>  
>
I agree with you. I would like something as `configure --help` for 
example `emerge -useflag foo`, portage parse USE description from the 
ebuild and output something similar to `configure --help`.


-- 
Tuan Van
Gentoo Net-Mail Team
GnuPG key: 6476B2FD
Key server: pgp.mit.edu
Fingerprint: 4CB6 83BD 32D1 BE77 FD14  400B D962 CD73 6476 B2FD


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2004-08-23 14:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-21 19:37 [gentoo-dev] New global USE flag: examples Matthieu Sozeau
2004-08-21 19:46 ` Norberto Bensa
2004-08-21 19:52   ` Ciaran McCreesh
2004-08-21 20:15     ` Norberto Bensa
2004-08-21 20:28       ` Ciaran McCreesh
2004-08-23 12:25         ` Paul de Vrieze
2004-08-21 22:43       ` Stroller
2004-08-23 12:23     ` Paul de Vrieze
2004-08-23 14:34       ` Tuan Van [this message]
2004-08-21 19:48 ` Ciaran McCreesh
2004-08-21 19:59   ` Carsten Lohrke
2004-08-21 20:11   ` Matthieu Sozeau
2004-08-22  0:27 ` Karl Trygve Kalleberg
2004-08-22  0:52   ` Michael Sterrett -Mr. Bones.-
2004-08-22  2:34     ` Karl Trygve Kalleberg
2004-08-22  3:44       ` Spider
2004-08-22  6:52         ` Mike Frysinger
2004-08-22 13:45 ` Matthieu Sozeau
2004-08-22 19:12   ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2004-08-22 23:28     ` Matthieu Sozeau
2004-08-23 12:30     ` Paul de Vrieze
2004-08-23 14:36       ` Mike Frysinger
2004-08-23 15:39         ` Matthieu Sozeau

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=412A008D.7010802@gentoo.org \
    --to=langthang@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