Re: [gentoo-user] Re: Which openoffice
* Uwe Thiem [EMAIL PROTECTED] wrote: On Monday 05 May 2008, Alan McKinnon wrote: OOo has just got to be the most fscked-up ebuild I've ever seen. I think you are being unfair towards the gentoo developers. It isn't the ebuild but OOo's build system (and source). The gentoo devs just try to work around its extreme fragility. ACK. Gentoo folks are not responsible for the OO-crap. Imagine, these OO jerks even ship their own compiler+glibc. Instead Gentoo folks deserve great honor for getting it built anyway. cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ - -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] Re: Which openoffice
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. Ciao Francesco -- Linux Version 2.6.25-gentoo-r2, Compiled #1 PREEMPT Sun May 4 08:26:42 CEST 2008 One 1GHz AMD Athlon 64 Processor, 2GB RAM, 2004.02 Bogomips Total aemaeth -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Re: Which openoffice
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
Re: [gentoo-user] Re: Which openoffice
On Monday 05 May 2008, Uwe Thiem wrote: On Monday 05 May 2008, Alan McKinnon wrote: OOo has just got to be the most fscked-up ebuild I've ever seen. I think you are being unfair towards the gentoo developers. It isn't the ebuild but OOo's build system (and source). The gentoo devs just try to work around its extreme fragility. Still, it builds just fine here. I let the build run overnight and have a fresh OpenOffice the next day. You sir, are completely correct. s/fscked-up ebuild/fscked-up build system/g There, now it's fixed. -- Alan McKinnon alan dot mckinnon at gmail dot com -- gentoo-user@lists.gentoo.org mailing list
