On Monday 05 May 2008, Francesco Talamona wrote:
> > > 2 - how long does it take to compile openoffice-bin
> > > on a PC with 2 GB Ram and a AMD Athlon-64 3200+ Processor?
> >
> > On my 2003 machine (AMD 2500+) 5 hours ;
> > on my 2007 machine (Intel Core-2 Duo 6700) 2 hours .
>
> Those are the timings of openoffice, openoffice-bin doesn't get
> compiled, it is "deployed", on my 2 GB amd 64 3200+:
>
>
> Sat Apr 19 14:40:43 2008 >>> app-office/openoffice-bin-2.4.0
> merge time: 2 minutes and 57 seconds.
OOo has just got to be the most fscked-up ebuild I've ever seen.
My old 2600+ MD Barton machine often took 18 hours to build (!)
So now I use OOo-bin, just don't try doing other intensive work
while "deploying" it. Here's what happens:
[EMAIL PROTECTED] ~ $ genlop -t openoffice-bin
* app-office/openoffice-bin
Fri Nov 9 09:27:59 2007 >>> app-office/openoffice-bin-2.3.0
merge time: 50 seconds.
Fri Jan 4 12:06:03 2008 >>> app-office/openoffice-bin-2.3.1
merge time: 35 minutes and 51 seconds.
Wed Apr 2 20:59:25 2008 >>> app-office/openoffice-bin-2.4.0
merge time: 1 hour, 5 minutes and 12 seconds.
The emerge in April also had two other emerges going at the same time -
a world update and a complete e17 rebuild. Nothing else showed a 6000%
increase in deploy time though....
Weird, huh?
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
