open office
development
We have a channel #go-oo on irc.freenode.net, where you can discuss development issues with hackers.
To contact anyone wrt. go-oo see the ooo-build maintainers or contact kendy T novell com
There is a mailing for ooo-build development. More info on how to subscribe or to read the archive. The mailing list have been migrated twice over the time, so you can see also the first old mailing list archive, and the second old archive.
You can download packages of OO.o here. These are tested to ensure clean builds.
ooo-build sources are stored in Git, more detailed instructions are available, but to simply check out the latest version of ooo-build:
Registered developers should use the following command to enable writing to the repository:
Once the source has been checked out, ooo-build can be built in very nearly the usual manner:
where DISTRO is the basename of a file in the distro-configs directory, such as Debian, SUSE, or Ubuntu.
Also note that running the ./download script will download additional files and packages over the net. Therefore, you need to have an active internet connection in order for this script to run successfully.
Please refer to this page for more information on how to build ooo-build from sources.
Find an overview over the last tinderbox build results here.
A list of the currently open tinderbox branches (CWSs and MWSs) can be found here.
For more information on branches, see the roadmap and codelines documents. To create your own tinderbox, check the Tinderbox setup guide.
Use CIA to look up the latest changes in the ooo-build git repository.
Our patches to sync bonsai via cvsup, and a description of how to make LXR work on RH 8.0+ can be found here.