Gentoo Archives: gentoo-dev

From: Fabio Erculiani <lxnay@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [OT] pkgcore bikeshed (was Portage team)
Date: Mon, 13 Jan 2014 09:32:45
In Reply to: Re: [gentoo-dev] [OT] pkgcore bikeshed (was Portage team) by "C. Bergström"
1 On Mon, Jan 13, 2014 at 10:15 AM, "C. Bergström"
2 <cbergstrom@×××××××××.com> wrote:
3 > On 01/13/14 03:43 PM, Alexander Berntsen wrote:
4 > Where I work uses pkgcore[1], but not the areas which are generally
5 > beneficial to the whole community. (We use it as part of a web application
6 > to handle testsuites which have build dependencies.) We can blah blah about
7 > performance of resolving package dependencies all day long,
8 > [...]
10 Not sure about what you mean with "blah blah". But given the amount of
11 both disk caches (metadata, vdb cache) and memory caches (the
12 in-memory aux_db cache that portage loads using pickle (it's a dict)
13 takes like 70-100Mb of RAM on an average desktop system), Portage can
14 still take *minutes* to calculate the merge queue of a pkg with all
15 its deps satisfied. Ironically, launching the same emerge command
16 twice, will take more or less the same time.
17 Yeah, this is probably bad design...
20 --
21 Fabio Erculiani


Subject Author
Re: [gentoo-dev] [OT] pkgcore bikeshed (was Portage team) "C. Bergström" <cbergstrom@×××××××××.com>
Re: [gentoo-dev] [OT] pkgcore bikeshed (was Portage team) Tom Wijsman <TomWij@g.o>