From: Stuart Herbert <stuart@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 14:52:38 +0000 [thread overview]
Message-ID: <200310271452.38111.stuart@gentoo.org> (raw)
In-Reply-To: <3F9E80C6.8020007@technaut.darktalker.net>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1143 bytes --]
On Tuesday 28 October 2003 2:44 pm, Andrew Gaffney wrote:
> Is there a way to determine how long it takes 'emerge' to parse an ebuild
> and figure out what packages it is dependent on according to USE flags? I
> wrote a Perl program that does this and it takes 0.049 seconds to parse
> '/usr/portagemedia-video/mplayer/mplayer-1.0_pre2.ebuild' and tell me what
> the dependencies are with the current USE flags. I want to compare it to
> how fast Portage does this on my particular setup to get an acurate
> comparison.
How about 'time emerge -p <package>'?
As an aside, the strace output of running an emerge or an ebuild makes
interesting reading.
Best regards,
Stu
--
Stuart Herbert stuart@gentoo.org
Gentoo Developer http://www.gentoo.org/
Beta packages for download http://dev.gentoo.org/~stuart/packages/
Come and meet me in March 2004 http://www.phparch.com/cruise/
GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319 C549 0C2F 80BA F9AF C57C
--
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-27 14:55 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 [this message]
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
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=200310271452.38111.stuart@gentoo.org \
--to=stuart@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