Re: Libreoffice and kde integration

Hi Michael,

On Mon, Dec 23, 2013 at 09:58:30PM +0000, Michael Meeks wrote:
> On Mon, 2013-12-23 at 21:10 +0000 wrote:
> > Why does the autogen.sh that is used to compile the  build, Linux - rpm (x86), 
> > version 4.1.4, English (US) have the flags -
>
>       Sure - this is because the rather old system we compile the generic
> linux builds on (which needs to be that old so we can run on all newer
> systems) can't feasibly have KDE4 installed. I tried to make a magic
> assembler tool to stub the libraries to overcome that without success -
> it's a bit of a pain.
>
> > --disable-kde4
> > --enable-kde
> >
> > in the file LibreOfficeLinux.conf.
>
>       Sure - and also --enable-gnome-vfs as well as --disable-gio is a
> similar disaster caused by the same issue.
>       It's all to do with what we can get to install on a reasonably vanilla
> CentOS 5 (IIRC).

Ah, I finally get what you were up too with that kde-stub-libs-foo. ;)

Just brainstorming, I wonder if it would be easier to do roughly what distros do
in these cases, for the 'integration' parts of LibreOffice that connect with
other infrastructure on the OS (mostly the above mentioned kde/gtk/gnome-foo),
namely: simply using a newer baseline.

Now using two baselines, one for 'core' LibreOffice which is truely ancient and
one for system integration, which is more recent, and building parts of
LibreOffice in each can be assumed to sounds like madness and probably is. Im
just not sure if using some symbols stubs lib approach is less painful in the
end.

Best,

Bjoern

P.S.: Note that the 'use two baselines' thing is likely easier than it sounds
as tools like pbuilder are around and automate most of that away.