Ariel Constenla-Haile wrote:
Hi,
On Tue, Dec 11, 2012 at 01:01:21PM -0800, Girvin R. Herr wrote:
"Choice" allowed me to continue updating the office suite!
I was using OpenOffice 3.3.0 when Apache took over. When Apache
released 3.4, I discovered Apache made some, IMHO bad, decisions
that broke installation on my older Slackware Linux computer. Those
decisions made it very painful for me to upgrade to their 3.4
version. The "deal breaker" was the decision to switch glibc
versions. Even though the release notes stated that OO 3.4 would
work on glibc 2.5 or greater, that was incorrect and in actuality,
it required glibc 2.11.
This wasn't a decision, it was a bug, see
https://issues.apache.org/ooo/show_bug.cgi?id=119385
Early testing by the user community would have avoided this bug. There
is no need to be a developer to contribute to an open source project
like OpenOffice.
Ariel,
Thanks for the update. I tend to gravitate toward processes that work,
so I have not been keeping up with this "bug" since I switched to LO.
The bug report does not seem to definitely state that this "bug" has
been addressed in the current or even future releases. That does not
give me a warm fuzzy feeling to return to AOO. As my time allows, I
will keep trying the new releases until they start working without
intervention. I would hope that the bug report recommendations will be
acted upon and AOO becomes more friendly to older Linux systems.
<snip>
The build environment based in dmake comes from Sun Microsystem times
(or may be even before that).
I wouldn't know about that. I have historically re-packaged the
downloaded binary packages into Slackware installation packages. After
the AOO 3.4 binary would not work, my attempt at building the source,
was to see if a working AOO 3.4 could be built against the libraries I
already have. I have found that if I can do that with any program, the
program will be the most stable. It was worth a try, but, as I said, it
failed. My computer log states that the failure was something to do
with a Python 5 module error (I have Python 2.5.2). There are only a
very few trusted binaries that I allow to run on my system. Normally, I
do build from source. However, the time involved with building a large
program such as AOO is a good driver to use it's binary. Besides, until
AOO 3.4, the binaries always worked well for me.
<snip>
Try the unofficial tar ball from
http://people.apache.org/~arielch/packages/r1372282-glibc-2.5/#full-archived-sets
you don't even need to install it.
Regards
Thanks, but for computer security reasons, I am _very_ reluctant to
install an unofficial version. I would prefer to wait until the
official, trusted, version is released. It is my impression, from more
than just this issue, that the AOO Linux effort is still a bit immature
and needs to settle down a bit before I can return to a stable AOO.
Thanks again.
Girvin Herr
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@openoffice.apache.org
For additional commands, e-mail: users-h...@openoffice.apache.org
