From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17690 invoked by uid 1002); 27 Oct 2003 14:45:36 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 6173 invoked from network); 27 Oct 2003 14:45:36 -0000 Message-ID: <3F9E80C6.8020007@technaut.darktalker.net> Date: Tue, 28 Oct 2003 08:44:22 -0600 From: Andrew Gaffney User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20031018 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gentoo Dev X-Enigmail-Version: 0.76.7.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [gentoo-dev] how long does it take portage to parse an ebuild? X-Archives-Salt: a8f56cad-b125-4834-8db1-f727582cfa68 X-Archives-Hash: 0d44eab3013bc30bee17c148ed4f3c5d 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