From: Douglas Russell <puggy@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Extra USE field
Date: Sun, 25 Jul 2004 22:33:06 +0100 [thread overview]
Message-ID: <200407252233.06345.puggy@gentoo.org> (raw)
In-Reply-To: <ce1317$akb$1@sea.gmane.org>
On Sunday 25 July 2004 20:52, Joel Konkle-Parker wrote:
> Would it be plausible to include an extra field in ebuilds that
> describes what effect a particular USE flag has on the package?
>
> Take, for example, "xml" and "xml2" in the xfree ebuild. Ok, the
> description says that it adds XML support. But why are there two of
> them? Why is it optional? What benefit does it have? etc.
>
> I can see something like:
>
> # etcat -u gnucash
> [ Colour Code : set unset ]
> [ Legend : (U) Col 1 - Current USE flags ]
> [ : (I) Col 2 - Installed With USE flags ]
>
> U I [ Found these USE variables in : app-office/gnucash-1.8.9 ]
> [snip]
> - - postgres : Adds support for the postgresql database
> Effect: Enables optional SQL backend for multiple simultaneous users;
> not currently maintained and does not support all features
> [snip]
>
> The postgres description by itself tells me nothing about why gnucash
> would need or want it, or what benefit it would have.
That would be really nice. I often wonder what the effect on a package is of a
use flag. Sometimes I really don't know if I want something or not.
Puggy
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-25 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 19:52 [gentoo-portage-dev] Extra USE field Joel Konkle-Parker
2004-07-25 21:33 ` Douglas Russell [this message]
2004-07-25 22:58 ` John Nilsson
2004-07-25 23:03 ` Joseph Booker
2004-07-25 23:23 ` John Nilsson
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=200407252233.06345.puggy@gentoo.org \
--to=puggy@gentoo.org \
--cc=gentoo-portage-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