Alex Schuster wrote:
Dale writes:
Peter Humphrey wrote:
On Thursday 28 July 2011 21:48:15 Dale wrote:
I have wondered that too. The process is sort of started but it's not
actually compiling either. I wonder how we could know for sure?
Easy. "emerge --fetchonly<blah>" first, then start the real work.
But if you emerge something and it has to be fetched first, is that
counted in the time genlop shows or not? That is the question. I don't
think it is counted but I'm not sure.
That's what I thought, too, but then I simply tried to be sure. Download
time _is_ counted.
Now we know. If I was on dial-up again, I could sure test that theory.
3KBs/sec would certainly make a difference. :-( Pardon me if I refuse
to go back tho. I like youtube to much.
I set mine to fetch in the
background so most of the time the fetch is done after a couple packages
gets compiled.
What about parallel emerges? I guess genlop will not take this into account.
I would think not. As long as the tarball is downloaded before emerge
gets to it to compile. I doubt it would even know how long it took to
download either.
Back when I was on dial-up, then I would fetch first. I did that
because my dial-up was so slow. It would take days to download OOo or a
major KDE upgrade.
We all remember, Dale. We all remember.
Wonko
Yea, me to. My puny DSL is a lot faster than dial-up. It's cheaper
too. That part is weird.
Dale
:-) :-)
