Hi Florian, Am Tue, 26 Apr 2005 18:32:31 +0200, schrieb Florian Heckl: >> - Who is in charge for the Mac OS X port. If you take a look at the >> mac porting webpage you might get the impression that still Edward >> Peterlin and Dan Williams are in charge or worse that nobody is in >> charge. So for outside developers and users a headless Mac Port is >> close to a dead Mac Port and they switch over to NeoOffice/J, iWork >> or stick with MSO. > Well, since Ed seems to fully concentrate on NeoOffice/J and > since we haven't heard from Dan in a while I suggest we need some > new people to be in charge of our port. Eric, you didn't suggest > anyone, so I suggest Eric Bachard. Any other suggestions?
I didn't suggest anyone because neither Eric Bachard nor I wanted to take an influence on the decision. >> - Next decision to be made is: Who does the official build for Mac >> OS X. Currently we have at least five people building OOo. Eric B., >> Pavel Janik, Maho Nakata, Florian Heckl and me. And I don't know if >> any of the other who tried and talked about it on IRC had any >> success. >> >> To make it worse it looks like all five or more builders use >> different sources, patches etc and so we cannot say that m9x or so >> works because it is possible that e.g. my and Eric B's builds work >> but Mahos don't or the other way round. We have to make official >> builds and let them pass official QA. For QA Joerg Sievers offered >> his help in his freetime when he is not employed at SUN. For QA we >> would have a person in charge. >> >> Since Maho has a sponosored G5 now best would be if he could build >> some languages and additional language packs. Eric B. proposed this >> on IRC. I don't know but afaik Maho uses the NetBSD porting >> mechanism. The question is if this mechanism is needed or not when >> an user only wants to use OOo and not build it. >> E.g. If you want to run a fink app you need to have fink installed. >> Only thing that makes me curious about Mahos build is that Terry >> Teague for the second time reported that he cannot open documents >> with Mahos builds. We have to investigate on this. Maybe I can ask >> Joerg to do an QA on Mahos build. > > I guess we should finally all agree to at least use the same > configure arguments (apart from languages) as long as we do not > have one official build. See my build instructions. These are mine ./configure arguments and I guess I have everything possible and building in them. What also would be important is to use the same patches or isn't it? Btw: What about your psprint patch? Is it still necessary in order to avoid installing (esp)ghostscript? I have tested your patch with m93 and I can say that it works and no ghostscript is necessary. Is there an issue filed for it or do we dismiss this idea and let the users install ghostscript. > Since Maho has a new G5 and already builds a lot, I would agree > that he could do our official builds once he gets no more > complaints about his builds not working for the one or the other. @Maho: The only problem I can see is that if mahos builds need pkgsrc this may prevent average mac users from installing them because they don't what it is and may be sceptic or if they know what it is we should make sure that pkgsrc don't affect an installed fink/Darwinports/gentoo or whatever other porting mechanism out there. So best would be if Maho does his builds under a "pure" Mac OS X and using no portig mechanism for building. He can use a porting mechanism for the needed depencies but please not for OOo itsself. > Maybe we should start using his builds rightaway so that he gets > all of our complaints from the start and can work on solving them? I will get his m96 and see if it fails here or not when it comes to opening documents. >> - Next point would be adding a decent installer that keeps it >> simple for Mac OS X users. Best would be to have this >> installer/launching app right out of the build process. A step in >> the right direction was Florian Heckl's Metapackage script that >> bundles the 17 single packages into one metapackage. Now it would >> be up to us to add the app Mox created into the installation >> process so that in the end you have an OOo.app and a click launches >> X11 and OOo. > > I think I will look what I can do here to both improve my script > and add what Mox has done. Thanks. >> In the meantime Stefan Taxhet tries to organize a Mac OS X >> Tinderbox. Eric B. gladly offered to host this Tinderbox. If we >> have this Tinderbox we can use it for official builds. Remote >> access for others and such stuff is to be planed when the Mac is >> there. If we don't get it we need to find another solution for a >> tinderbox and an official build machine. While writing this answer Joerg Sievers gave feedback that he is also willing to maintain the tinderbox. Now that we have the choice its up to us to decide. Regards, Eric Hoch -- ## Ansprechpartner Anwenderunterst�tzung, users-Mailingliste, MacOSX ## de.OpenOffice.org - Office f�r MacOS X, Linux, Solaris & Windows ## Openoffice.org - ich steck mit drin! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
