On Fri, Sep 26, 2003 at 09:12:30AM +0530, Jason E. Stewart wrote: > Definately. Thanks for the update. It would be a big help if folks > could update the bug with a status report - just to let folks like me > know that work is progressing, it's really the only interface any of > us have into what's going on. OK, well I'll give you a bit more information about the powerpc builds. Up until now there has not been a powerpc machine available which we could use to build OOo on. Volatire is the only DD-accessible machine, and the disk space is too limited to provide chroots or to build OOo there. Now the folks at freenet.de have kindly donated a machine, bruckner.debian.org, which is available to DDs, and is also there for the OOo team to use. Rene & I are now working through a build of the current rc5 version, so with luck we may be able to upload rc5-1 for powerpc at the same time as i386. If you want to follow progress more closely, hang out on our IRC channel (#debian-oo). That's where we co-ordinate the day-to-day work. I'm having trouble keeping up with all the bugreports - 72 outstanding, and I don't have all of them in my head, so please bear with me if I forget to keep them all up to date. Seriously, I don't have enough time available to deal with all these bug reports and keep up to date, and deal with all the build problems, and integrate patches, and etc etc, so help in any of these areas would be useful. > Is there anything that I could do to help? Yes, there's plenty. It depends what your skills are, and what you want to do. Any job that you can take off our hands can help free up more time for us to concentrate on the building tasks, so even if you do not directly work on the powerpc builds you can help out. A task list in rough order of difficulty/skills/time required: * Documentation updates: keeping docs such as README.Debian/TODO up to date. * Website updates: Jan doesn't have time to work on the web site any more, but the site is available in CVS now. * Bug upstreaming: Trying to reproduce open bugreports, checking whether they apply to the upstream version, searching for open reports upstream and filing new bugs where necessary. * Testing builds: Keeping up to date with the packaging CVS and trying out builds on different architectures. It helps if you are capable of making minor fixes yourself. Also, testing the current CVS on Woody to find out what needs fixing for the backport. * Fixing bugs. * Testing possible new build changes, such as recompiling with increased optimisation (-O3) or compiler flags. * Further integration with the Ximian builds. We have merged the patching mechanism, but the build scripts are still separate, with Ximian's building scripts in ooo-build/bin and debian's in debian/rules. That should be enough to get started :) I'll try and put this up on the website somewhere when I get time.. Chris
Attachment:
pgpotNtQ17bRJ.pgp
Description: PGP signature