From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j3TEBBTN004557 for ; Fri, 29 Apr 2005 14:11:11 GMT Received: from stargazer.weeve.org ([24.8.204.228]) by comcast.net (sccrmhc12) with SMTP id <2005042914111601200dd5pre>; Fri, 29 Apr 2005 14:11:16 +0000 Date: Fri, 29 Apr 2005 08:11:12 -0600 (MDT) From: Jason Wever To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Portage ebuild cruft In-Reply-To: <200504292258.13394.jstubbs@gentoo.org> Message-ID: References: <200504281840.23788.lanius@gentoo.org> <5a67a16f050428161738959aa1@mail.gmail.com> <200504292258.13394.jstubbs@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archives-Salt: ff8ca6c1-c367-4bf7-a26c-47b0b3c8aa70 X-Archives-Hash: 90a70116d1c852ba925eb42620a0749c -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 29 Apr 2005, Jason Stubbs wrote: > The initialization time of portage is directly related to the number of > packages installed. Cutting out excess ebuilds from the tree won't speed this > up at all. Cutting out excess ebuilds won't have much effect on the general > running of emerge at all, actually, except for updating the cache after > syncing. Does that include the about >=10 second delay when emerge is first run on a box after a reboot before you get any visible output on the screen, or is that an entirely different problem? - -- Jason Wever Gentoo/Sparc Co-Team Lead -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCckCCdKvgdVioq28RAlJ6AJ0bf2NHAFr6Otc7v0HvbyqOlb7DDgCfYrTR 6tFh38nSUwVw6XDXvYnWmxk= =ODsL -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list