SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
+1 for that. KOffice is one of the few package I uninstall from a stock Slackware install.
I think many of us share that sentiment. I recently had a user induced loss of OS while working on the road. Luckily I had an install disk (thanks Bob for the current_mirror script that makes iso's as well) The motel only had .25 mb/s down. I tried for an hour to make koffice work with my invoice spreadsheet, but in the end had to download OOo overnight. Libre office looks interesting, but for the time being GoOO works well here. Now to figure out how to add that to the installation disk.............
With all due respect, could you translate that into English?
Its the channel topic for the go-oo IRC channel in the freenode network.
It says that go-oo is deprecated and development switched to LibreOffice now.
Michael Meeks is a Novell employer, previously responsible for go-oo.
Today he is part of the leading team of developers working in LibreOffice.
You can read a very interesting interview of his about LibreOffice at LWN
After reading about Eric's travails building LibreOffice, and my own grustrtions with Go-OO several months back (until somebody posted a good SlackBuild for it), I have to wonder why the source code isn't organized in a way that makes it easier to build.
For developers, we are open for business - we have a realistic view of the code-base and as such we are interested in including people's fixes and improvements quickly. When we can get people working to clean up the code, translate German comments, remove dead code, fix ergonomic nits, write unit tests and so on - we are optimistic that we can produce a far better product, and one that (as developers) we can be proud of.
Linux distributions should find LibreOffice easier to package, as the development team has a vast amount of Linux distribution experience.
All of that of course leads to getting a better, more stable, and featureful office suite into users' hands.
The other thing I wonder about is where things are going with the OO.org user interface update project. There was a lively debate around that project on how to update the user interface to make things better and whether or not to mimic Microsoft Office's new UI.
With all of that as background, and with LibreOffice being a fork, I have to wonder just how much of Open Office's code they're going to use in the future.