CentOS - Jul 2007 - openoffice

Since rpm from openoffice.org was not nicely integrate with Centos, what is
the best way to make OO uptodate, can i use (or depend on) package from fedora
(it slightly
outdate but not too far from OO release).

Having see the huge spec file (around 3700 lines), building it ourself is
really not fun :(


--beast

On 7/27/07, beast <beast at ldap.or.id> wrote:
> Since rpm from openoffice.org was not nicely integrate with Centos, what is
> the best way to make OO uptodate, can i use (or depend on) package from
fedora (it slightly
> outdate but not too far from OO release).
Which version of centos?
Why do you need to do this? The version in centos provides bug/security fixes.
> Having see the huge spec file (around 3700 lines), building it ourself is
> really not fun :(
No, OOo is a huge PITA to build and takes forever, even on some really
powerful systems.

-- 
During times of universal deceit, telling the truth becomes a revolutionary act.
George Orwell

beast wrote:
> Since rpm from openoffice.org was not nicely integrate with Centos, what is
> the best way to make OO uptodate
I have not tried to integrate the newest OOo2 into CentOS-5 (or even
CentOS-4.5) since both have OOo-2.0.4 integrated.  Are there REALLY that
many new features that you MUST upgrade from a Stable 2.0.4 to a new 2.2.x?

I can try to do it on CentOS-5 (Use the OOo RPMS from the openoffice.org
site) and post how it went here.

, can i use (or depend on) package from
> fedora (it slightly
> outdate but not too far from OO release).
> 
Well ... you would have to rebuild a newer version other than the one on
FC6 ... which MIGHT still work on CentOS-5.  However, in the future as
tomcat, glibc and other build requires diverge between FC6 and CentOS-5
it will be less likely to work.

In a 8 months when there is no more FC6 support, that will stop working
anyway.

So, the best bet would be to either use the CentOS version (which will
get security updates for it's lifetime ... and which MAY get some
enhanced features) === OR === create a process to use the OOo RPMS
directly from the OpenOffice.org website.
> Having see the huge spec file (around 3700 lines), building it ourself is
> really not fun :(
And building a NEWER one from Fedora7 / Rawhide will be quite hard
because of the Versions of packages for the Requires and BuildRequires.

Thanks,
Johnny Hughes

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20070727/0cd7b627/attachment.sig>

On 27/07/07 10:13 -0500, Johnny Hughes wrote:
>I have not tried to integrate the newest OOo2 into CentOS-5 (or even
>CentOS-4.5) since both have OOo-2.0.4 integrated.  Are there REALLY that
>many new features that you MUST upgrade from a Stable 2.0.4 to a new 2.2.x?
Not today, but next year OOo 2.0 will be outdated and if asking for a support
most people will ask to get the latest version. 
My reasons is because the recent OO provides better compatibility with the
latest MS
Office, since it is a critical to our company which exchange the document in
MS office format with the customer.
>Well ... you would have to rebuild a newer version other than the one on
>FC6 ... which MIGHT still work on CentOS-5.  However, in the future as
>tomcat, glibc and other build requires diverge between FC6 and CentOS-5
>it will be less likely to work.
>
>In a 8 months when there is no more FC6 support, that will stop working
>anyway.
This is what i'm worry about...
>=== OR === create a process to use the OOo RPMS
>directly from the OpenOffice.org website.
>
I also thinking this is the best possible solution. 
Get the OO package from openoffice.org site and then add desktop integration
ourself.
But, will it mess up the whole thing when we i do 'yum upgrade'?


--beast