From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE flags information resource
Date: Tue, 2 Jan 2007 09:37:15 +0200 [thread overview]
Message-ID: <200701020937.15944.alan@linuxholdings.co.za> (raw)
In-Reply-To: <7bef1f890612311952g5440581dmba74ef95ab6cee65@mail.gmail.com>
On Monday 01 January 2007 05:52, Alan E. Davis wrote:
> On 12/31/06, Aniruddha <mailing_list@planet.nl> wrote:
> > I think this is an excellent idea! For starters you can use euse:
> >
> > # euse -i useflagname
>
> I already use euse. It is really helpful. The short descriptions
> of the USE flags are often helpful. Just as often, they are not
> informative enough to enable me, at least, to make an informed
> decision. A little more information would often have helped.
>
> Do you have any ideas about a next step?
>
> Alan
AFAIK the only references to what the flags mean
is /usr/portage/profiles/use.desc. To find out more, read the ebuild to
see/divine what the developer has in mind with that flag. For instance,
kdebase-3.5.5-r3 has amongst others the following:
DEPEND="arts? ( ~kde-base/arts-${PV} )
>=media-libs/freetype-2
media-libs/fontconfig
pam? ( kde-base/kdebase-pam )
>=dev-libs/cyrus-sasl-2
ldap? ( >=net-nds/openldap-2 )
cups? ( net-print/cups )
...
So you would have to look into those various optional packages, find out
what they are, then look into kdebase a bit deeper and find what it
does with those optional packages. For example, the 'ldap' flag causes
kdebase to be built against net-nds/openldap.
The point is that it's simply not possible to give detailed info about
USE flags most of the time, and some intense RTFCing and research is
involved
alan
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-02 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 1:38 [gentoo-user] USE flags information resource Alan E. Davis
2006-12-27 2:00 ` Thomas Tuttle
[not found] ` <4597A9E7.10505@planet.nl>
2007-01-01 3:52 ` Alan E. Davis
2007-01-01 11:25 ` Strong Cypher
2007-01-02 7:37 ` Alan McKinnon [this message]
2007-01-02 13:35 ` Alan E. Davis
2007-01-02 14:59 ` Alan McKinnon
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=200701020937.15944.alan@linuxholdings.co.za \
--to=alan@linuxholdings.co.za \
--cc=gentoo-user@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