I just came to think of a very useful feature to portage, and I'm sure someone has to have thought of it in the past. When we emerge a lot of packages, emerge will calculate dependencies, make a list of packages to build (in order), and then begin the cycle:
- download package #1 - build/install package #1 - download package #2 - build/install package #2 etc... Wouldn't it be smarter if it would split this in 2 threads, one for downloads and one for builds? So, it would download package #1, and as soon as it finished, it would start building package #1 AND downloading package #2. Downloading doesn't take CPU time, and building doesn't take bandwidth. So, why not do both at the same time? I can't think of a reason for this to fail or cause errors (not caused by the current system). What do you think about it? -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil |
msg01953/pgp00000.pgp
Description: PGP signature
