OpenOffice.org 2.0 is the productivity suite that individuals, governments, and corporations around the world have been expecting for the last two years. Easy to use and fluidly interoperable with every major office suite, OpenOffice.org 2.0 realises the potential of open source.

With new features, advanced XML capabilities and native support for the OASIS Standard OpenDocument format, OpenOffice.org 2.0 gives users around the globe the tools to be engaged and productive members of their society.

Download it now. If it is not ready today in your language, it will be shortly. OpenOffice.org 2.0 is yours.

And openoffice-bin is in portage already!

Update 21-10-2005:
The openoffice source ebuild also hit portage now!

Happy merging

Last edited by Q-collective on Fri Oct 21, 2005 7:40 am; edited 2 times in total

Ok, let's see what takes longer. To wait for the ebuild, or to emerge it?

Cheers,
Drag0n_________________"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook

For those of you who already installed OOo2 as Release Candidate 3: help to save Bandwidth!
As the final release is exactly the same to RC3 you can just rename the installation file to save time and bandwidth of a 100MB download!

For those of you who already installed OOo2 as Release Candidate 3: help to save Bandwidth!
As the final release is exactly the same to RC3 you can just rename the installation file to save time and bandwidth of a 100MB download!

Cheers,
Drag0n_________________"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook

Actually, the question might be... how long will it take for me to find out this doesn't work....

Or better still how long will it take to load after it is installed? In my case it takes whooping great 1min 20secs from when I click writer on the kde menu untill writer actually appears. That on an AMD 64 2800 with 512Mb of ram and a SATA hardisk. That time is unacceptable!
Edit: Just got that startup time down to 3 seconds by pointing to java in the options

Last edited by pinr on Thu Oct 20, 2005 9:38 pm; edited 2 times in total

No idea if it because I whacked my own ebuild together or if it's a cflags problem. I normally use the -bins and I mainly wanted to evaluate two things.
A) What's the compile time on my system and B) Is it even worth it (feature or performance wise) to use the compiled version over the binary install.

So, anyway, I left mine nicely compiling the official stuff at work and it should be nicely finished by the time I go back in the morning. If it still crashes it's back to the -bin versions for me._________________--

One question though: How can I get the negation symbol for the "exists" quantor? To clarify what I mean, in LaTeX this would be \not\exists. Not that I like typesetting formulae with anything other than LaTeX, but I'm just curious.

Cheers,
Drag0n_________________"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook

I've been waiting for this release to emerge openoffice. Only took 6 and a half hours to compile on a basically stable x86, Athlon XP 2600+ 1.91Ghz Barton core, 768MB PC2700 DDR ram system Played around with it a bit and so far is very stable and fast. _________________When the plague descends from Heaven above only Darkness will be your one true ally.