From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] use foo && bar vs. [ `use foo` ] && bar
Date: Mon, 19 Jul 2004 18:44:24 +0100 [thread overview]
Message-ID: <20040719184424.18122f2f@snowdrop.home> (raw)
In-Reply-To: <20040719173349.GA26225@earwig.bogus>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Mon, 19 Jul 2004 18:33:49 +0100 Tom Knight <tomk@gentoo.org> wrote:
| Back on topic, I've searched for this on bugzilla, and didn't find
| anything, but I'm sure it's come up on the forums before. There are
| several ebuilds which have something along the lines of:
|
| use foo && bar
This is correct.
| Which executes bar if the foo USE flag is set, the problem is that the
| use function not only returns true when the USE flag is set it also
| echos the flag to stdout. When you emerge something you end up with
| loads of use flags outputted.
This is about to change. In the future use will be silent and usev (?
can't remember whether it's a v...) will output.
| The solution is to do it like this:
|
| [ `use foo` ] && bar
Don't do that.
| I'm going have a go at fixing some of the net-mail packages, if others
| can do the same taht would be great.
Don't. You'll just have to un'fix' it again later :)
--
Ciaran McCreesh : Gentoo Developer (Sparc, MIPS, Vim, Fluxbox)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-19 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 17:33 [gentoo-dev] use foo && bar vs. [ `use foo` ] && bar Tom Knight
2004-07-19 17:44 ` Ciaran McCreesh [this message]
2004-07-19 17:48 ` Tom Knight
2004-07-19 20:34 ` Mike Frysinger
2004-07-19 20:53 ` Stuart Herbert
2004-07-19 22:13 ` Mike Frysinger
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=20040719184424.18122f2f@snowdrop.home \
--to=ciaranm@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