On Fri, 2003-02-21 at 09:34, Bruno Lustosa wrote: [snip] > 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?
I think this was brought up a while ago. My housemate still moans about it, and won't switch from debian (I'm trying!) The problem I see is, what happens when #1 finishes compiling, but #2 hasn't finished downloading? But I'm sure a smart developer type could get around that with some fancy threading type stuff, or something. I still think it would be a very helpful addition. -- Mike Williams <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
