Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 75367 - emerge shound run downloading in background to boost installation time
Summary: emerge shound run downloading in background to boost installation time
Status: RESOLVED DUPLICATE of bug 1661
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Conceptual/Abstract Ideas (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-22 13:58 UTC by Artur Wronski
Modified: 2005-07-17 13:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Artur Wronski 2004-12-22 13:58:19 UTC
When I execute 'emerge package_name' (e.g. emerge gnome), emerge run run into loop:
1) download pacakge x
2) compile package
3) goto 1)

This is very bad solution because installation of complex packages, like kde, gnome, etc. is two times longer then is should be!

Reproducible: Always
Steps to Reproduce:
look how installation of complex packages looks


Actual Results:  
I wait two times longer than I should while installing things :-)

Expected Results:  
Emerge should download first pacakge, than should start compiling it. It the
same time it should start downloading the rest of packages. It's correct
solution because compilation is only cpu consuming and downloading is only
bandwidth consuming so there are independed.

Compilation shouldn't be suspensed while downloading and vice versa.

If downloading stops first there will be no problem, compilation will go on. If
compilation is faster than downloading it should stops and wait for next package
if it's not available in current moment. 

I've made some test and on my machine compilation time of KDE for example would
change from 7h to 4h when compilation and downloading is synchronous.
Comment 1 SpanKY gentoo-dev 2004-12-23 06:04:56 UTC

*** This bug has been marked as a duplicate of 1661 ***