From: Yannick Koehler <yannick.koehler@colubris.com>
To: Wilbert Berendsen <wilbert@oswf.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: IUSE variable clarification
Date: Thu, 9 Jan 2003 12:06:21 -0500 [thread overview]
Message-ID: <200301091206.21417.yannick.koehler@colubris.com> (raw)
In-Reply-To: <200301091800.57824@oswf.org>
Le January 9, 2003 12:00 pm, Wilbert Berendsen a écrit: / On January 9,
2003 12:00 pm, Wilbert Berendsen wrote:
> On Thursday 09 January 2003 17:44, Burton Samograd wrote:
> > It looks to me like I got two different responses from different gentoo
> > (...)
> > If the ebuild I'm writing has a depend line:
> >
> > DEPEND="ncurses # required
> > ssl? libssl" # optional
> >
> > according to the first response IUSE would be
> >
> > IUSE="ncurses ssl"
> >
> > and for the second it would be:
> >
> > IUSE="ssl"
> >
> > Could someone please clarify? It seems to me that the second is correct
> > since the first can already be inferred from the depend line, but if the
> > compile on USE change feature is only using the IUSE variable then the
> > first would be correct.
>
> The second one is correct I think. I think of IUSE as Interactive USE.
> Interactive programs (eg Kportage) can read IUSE and immediately present
> the user the applicable flags before starting an emerge.
>
> So IUSE contains only the used USE settings, not the dependencies.
Wouldn't it be interesting as well for portage/emerge to be able to display
the content of the IUSE to the end-users?
For example, emerge -i vi could display the corresponding IUSE content so that
a user can make a better choice when emerging that package?
--
Yannick Koehler
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-01-09 17:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 14:31 [gentoo-dev] IUSE variable clarification Burton Samograd
2003-01-08 14:59 ` Maik Schreiber
2003-01-09 16:44 ` Burton Samograd
2003-01-09 17:00 ` [gentoo-dev] " Wilbert Berendsen
2003-01-09 17:05 ` Maik Schreiber
2003-01-09 17:06 ` Yannick Koehler [this message]
2003-01-09 17:03 ` [gentoo-dev] " Maik Schreiber
2003-01-08 15:04 ` Nick Jones
2003-01-08 19:18 ` Terje Kvernes
2003-01-08 19:52 ` Felipe Ghellar
2003-01-08 20:11 ` Terje Kvernes
2003-01-09 15:42 ` Paul de Vrieze
2003-01-09 21:05 ` Bob Phan
2003-01-09 22:35 ` Paul de Vrieze
2003-01-10 12:28 ` Bob Phan
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=200301091206.21417.yannick.koehler@colubris.com \
--to=yannick.koehler@colubris.com \
--cc=gentoo-dev@gentoo.org \
--cc=wilbert@oswf.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