Gentoo Archives: gentoo-dev

From: Nirbheek Chauhan <nirbheek@g.o>
To: gentoo-dev@l.g.o, Arfrever Frehtes Taifersar Arahesis <arfrever.fta@×××××.com>
Subject: Re: [gentoo-dev] Re: proj/portage:master commit in: pym/portage/dbapi/
Date: Sat, 26 Nov 2011 11:27:43
In Reply to: [gentoo-dev] Re: proj/portage:master commit in: pym/portage/dbapi/ by Fabian Groffen
On Sat, Nov 26, 2011 at 4:28 PM, Fabian Groffen <grobian@g.o> wrote:
> On 26-11-2011 01:54:35 +0000, Arfrever Frehtes Taifersar Arahesis wrote: >> commit:     1d4ac47c28706094230cb2c4e6ee1c1c71629aa0 >> T> Org> >> AuthorDate: Sat Nov 26 01:52:49 2011 +0000 >> Commit:     Arfrever Frehtes Taifersar Arahesis <arfrever <AT> gentoo <DOT> org> >> CommitDate: Sat Nov 26 01:52:49 2011 +0000 >> URL:;a=commit;h=1d4ac47c >> >> dblink.mergeme(): Merge files in alphabetic order. > > What's the advantage of this?  I don't really like to pay for sorting a > potentially huge list just for some eye-candy.  (That's omitted by > default these days anyway...) > Any other opinions on this one? >
If it should be sorted[1], it should really be sorted in the reverse order of distfile-download size. That would be extremely useful on systems with slow internet connections. Too many times have I sat waiting for libreoffice-bin to download while a webkit-gtk recompile waits in the queue. We already have the information during dependency resolution with --verbose, and it costs very little. Besides, sorting even 30,000 entries (if you're merging every ebuild in portage) should not take more than a few secs. 1. I'm obviously assuming that dep nodes that do not depend on each other would be sorted -- ~Nirbheek Chauhan Gentoo GNOME+Mozilla Team