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