Slashdot Mirror
OpenOffice.org For Mac OS X Hits 1.1.1 (Finally)
berchca writes "So it looks like OpenOffice.org for Mac OS X has finally hit 1.1.1 (for X11). They've also stated they probably won't do a native (Aqua/Carbon) release until OOo 2.0 is out, in late 2005 or early. Great work guys! Now I can get decent macros." I hope 1.1.1 has some speedups over 1.1.0, which works well but takes forever to start.
well, I'll tell you what, I had exactly the same idea as this guy last night and tried to download the subversion package, and gave up half way through recompiling the new version of Fink (WTF, I just downloaded it as binary and it wants to download (AND COMPILE!!?!?!?!?!?!) a new version of itself??). You're about as helpful as the myriad documents I had to plough through to get that far.
It's a mess, and if you're used to that kind of software deployment and want to put up with it, great, but frankly, it's about 10 years behind the rest of the world. I don't mind messing around on the command line to get a command line tool up and running, but what's with this 'auto-update' that actually has to compile most of the software again and a graphical client that doesn't even manage to hide the command line (please type in your response (what, you mean, like on a command line but with a little dialog that gets in the way?)) and has lots of cryptic menus (selfupdate-rsynch)? Yes, I *can* go away and find out what the menus in the app mean, but it's a tool for getting new software, not photoshop; I'd expect the menus etc to be straightforward and legible for someone who's not familiar with the program. It could at least have chosen a default update method rather than sticking at that point. The flat file layout (just like on the command line then, how about nested trees of categories at least?) and basic GUI I could put up with, but it took two hours to get software that should have been painless to install.
Why exactly should I have to download and compile a new version of software and all the libraries it depends on just after I've downloaded the binary?? Then it gives me messages like this... (note the mistake (at least I damn well hope so) in file size). The only advantage is the dependency checking, which it doesn't even seem to work all the time.
Need to get 4933kB of archives. After unpacking 1980MB will be used.
Take a look at bundles on OS X (ship the used version of the library with the app, in a nice neat package), then look at fink and tell me it *just works* if you know what you're doing. For certain values of knowing what you're doing, yes it just works. I think the point of the parent poster was that he doesn't want to have to go through all that pain just to try out some software. Not that he can't 'learn fink' but that he doesn't see the benefits which repay all that effort. Ah, I must go, I have another 'please provide your response to the command line' message.