From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] how long does it take portage to parse an ebuild?
Date: Mon, 27 Oct 2003 11:06:29 -0500 [thread overview]
Message-ID: <200310271106.40711.vapier@gentoo.org> (raw)
In-Reply-To: <3F9E8B36.3000402@technaut.darktalker.net>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 503 bytes --]
On Tuesday 28 October 2003 10:28, Andrew Gaffney wrote:
> Mike Frysinger wrote:
> > On Tuesday 28 October 2003 10:04, Andrew Gaffney wrote:
> >>Is there a quicker
> >>way to determine the USE flags on the fly?
> >
> > portageq envvar USE
>
> That take twice as long to run as 'emerge info | grep USE'.
so the way may not be quicker, but portageq is the way you're supposed to get
portage related information for scripts and stuff ...
file a bug that it currently isnt very fast ;)
-mike
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2003-10-27 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 14:44 [gentoo-dev] how long does it take portage to parse an ebuild? Andrew Gaffney
2003-10-27 14:52 ` Stuart Herbert
2003-10-28 15:04 ` Andrew Gaffney
2003-10-27 15:13 ` Mike Frysinger
2003-10-28 2:30 ` Andrew Gaffney
2003-10-28 20:17 ` Marius Mauch
2003-10-28 15:28 ` Andrew Gaffney
2003-10-27 16:06 ` Mike Frysinger [this message]
2003-10-27 16:08 ` Peter Ruskin
2003-10-28 23:59 ` Andrew Gaffney
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=200310271106.40711.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@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