From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23814 invoked from network); 7 Aug 2004 11:22:10 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 7 Aug 2004 11:22:10 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BtPH6-0001HD-7G for arch-gentoo-dev@lists.gentoo.org; Sat, 07 Aug 2004 11:22:08 +0000 Received: (qmail 17636 invoked by uid 89); 7 Aug 2004 11:22:07 +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 25190 invoked from network); 7 Aug 2004 11:22:07 +0000 From: Jason Stubbs To: gentoo-dev@lists.gentoo.org Date: Sat, 7 Aug 2004 20:25:09 +0900 User-Agent: KMail/1.6.82 References: <200407311309.53381.jstubbs@gentoo.org> <200408070857.29263.jstubbs@gentoo.org> <200408071207.32753.chrb@gentoo.org> In-Reply-To: <200408071207.32753.chrb@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200408072025.09421.jstubbs@gentoo.org> Subject: Re: [gentoo-dev] Dynamic SLOTs X-Archives-Salt: f2a23bae-a0e2-42f0-a1a4-b4b6abd7c3d2 X-Archives-Hash: af357bd18c30150bafee10375117149a On Saturday 07 August 2004 20:07, Chris Bainbridge wrote: > On Saturday 07 August 2004 00:57, Jason Stubbs wrote: > > Even with all that, a full dependency tree is built with all circular > > dependencies resolved in about 6 seconds, where currently emerge takes > > about 2 seconds. I can't see a way to get USE-based SLOTs in without at > > least doubling that figure (which is incidentally the time that 2.0.50 > > took). I'm open to suggestions on how to get around it. > > Maybe I'm not understanding this fully, but couldn't you just compute the > dependency tree once and then cache it? And allow quick updates to the > cached info by only editing dependency links for a single ebuild when it > changes. You'd need to cache the dependencies for different sets of use > flags as well. The dependencies of a single package with a single set of conditions don't take long to calculate. The issue is that, real soon, packages are going to be able to specify some of those conditions for other packages. Figuring out the best combination of packages/conditions and whether it is indeed possible (ie. no conflicts) is what takes the time. Regards, Jason Stubbs -- gentoo-dev@gentoo.org mailing list