Posted: Mon Nov 22, 2004 11:06 am Post subject: OOO Bug 31072 - 1.1.2 installer failing on convert_lucida.sh
I know this bug is well documented here but, I need to get some votes on OOO's website for this one. If anybody can please spare some OOO votes, please rank this one up on the OOO website:
http://qa.openoffice.org/issues/show_bug.cgi?id=31072
This bug is a real blocker for anybody who has any quams with installer errors. More votes means more people care about OOO on OSX and this can only help us Mac'ers getting OOO for OSX sooner. I know the installer is just for 1.1.2 but still, exposure is still exposure. Show your support. Put in your vote!
Adding votes sure isn't going to help get this issue fixed because the engineers at Sun assigned this bug to me yet I didn't write the installer nor do I have the source code. Even worse, Sun's engineers keep limiting my IssueZilla privileges so that I can only submit and query bugs so I cannot reassign it to anyone else.
Seems to me that you will have more immediate results using Neo/J instead of waiting for a new OOo X11 installer to appear.
Posted: Mon Nov 22, 2004 2:58 pm Post subject: Re: Thanks for the reply
JavaDude wrote:
Is it possible to at least post this to the bug so that maybe it gets a little more attention. It's totally sad the poor support for OSX builds. :[
I sure hope they have more focus after 2.0 stablizes and we finally get a native port.
Something that is not widely understood about OOo (and the OOo Mac port) is that Sun employs an entire small company of engineers (the former company StarDivision) to work on StarOffice/OOo on Windows, Solaris, and I think Linux. By contrast, the Mac porting effort is entirely volunteer. And the number of volunteers is very, very small. At any given time, there are fewer than a half-dozen "developer types" "working" on any form of OOo for the Mac.
Without substantial funding and an increased number of developers, there's no way that the Mac effort can keep up with the massive amount of code changes created by the company of Sun engineers, build (it takes a long time to build even when a build works), QA the build, make and QA an installer (and Apple's installer can't handle all of the things needed to install OOo on both 10.2 and 10.3; that's why there's the ZeroG installer that has proved so problematic--but hey, at least ZeroG donated a license for it; otherwise we might be downloading five separate installers and running terminal commands to install OOo!), and then support the final release and its installer. On top of all of this, there is a faction within the OOo community that is either simply ignorant of Mac needs or openly hostile.
The fact that we even have a Mac OOo in the face of all of these obstacles is a miracle IMHO.
Because it is so difficult to add needed Mac features to the ever-changing OOo itself (even simple patches sit around for months/years waiting to be committed, and then sometimes older patches fail to make it into new versions, etc.), some of the core developers who got the Mac port going started the NeoOffice project(s) to work on adding native Mac features to OOo, and they work (between major OOo releases in some cases, all the time in others) on creating an Aqua Mac "OOo." Because of that strategy, we now have NeoOffice/J (the most stable, end-user-focused of the two NeoOffice projects, and the only one under active development now) with native Aqua menus, native ATSUI font rendering and language/keyboard support, native print dialogues, scroll-wheel support, and so forth. All done on a volunteer basis.
Having said all of that, the installer bug has gotten lots of attention here. The fact that 1) it didn't show up in our QA'ing the installer and 2) there are several fairly easy work-arounds posted in the installer FAQ and installer FAQ thread means (IMO) that this was a lower-priority issue than, say, adding Aqua menus to NeoOffice/J. In a perfect world there would be enough resources so that there are enough setups tested where this issue would have been caught before release, or where every OOo release could have a Mac release (at the same time!) and the bug could be fixed in the next release, or even where a new installer for 1.1.2 could have been spun. Unfortunately, there's one guy building the installer and a half-dozen or so of us who tested the installer and the build (we caught a few bugs, including some Mac-only crashers, and found some work-arounds for unfixable installer issues, but that's not enough).
Secondly, I think the "focus" of those Mac devs who know the OOo code is where it should be right now, and I think if you try NeoOffice/J, you'd agree
Finally, it's obviously hard to tell "tone" from forum posts (so apologies if it's just frustration rather than something else), but "complaining" on trinity that "they" aren't attentive enough or properly focused is not likely to win many friends since most of the people who respond to posts here are either 1) the developers who volunteer their time to make OOo/Mac (in its various forms) a reality or 2) non-developer folks who've volunteered their time to do QA on releases and to answer support questions.
(I speak for no one but myself in this thread--not for the OOo community, the Mac OOo devs, not the Mac OOo/Neo community, nor even the rest of the testers.)
Posted: Tue Nov 23, 2004 1:23 am Post subject: Re: Installer bug
pluby wrote:
Adding votes sure isn't going to help get this issue fixed because the engineers at Sun assigned this bug to me yet I didn't write the installer nor do I have the source code. Even worse, Sun's engineers keep limiting my IssueZilla privileges so that I can only submit and query bugs so I cannot reassign it to anyone else.
As well as agreeing with other sentiments expressed in this thread, I have unburdened Patrick of this bug
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
