From: Andrew Gaffney <agaffney@technaut.darktalker.net>
To: Gentoo Dev <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] how long does it take portage to parse an ebuild?
Date: Tue, 28 Oct 2003 08:44:22 -0600 [thread overview]
Message-ID: <3F9E80C6.8020007@technaut.darktalker.net> (raw)
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.
--
Andrew Gaffney
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-10-27 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 14:44 Andrew Gaffney [this message]
2003-10-27 14:52 ` [gentoo-dev] how long does it take portage to parse an ebuild? 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
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=3F9E80C6.8020007@technaut.darktalker.net \
--to=agaffney@technaut.darktalker.net \
--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