Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


I see. Yes I am installing the deb packages downloaded from TDF.

Optimisation was the main reason I was cherry picking the packages, and
since Libreoffice comes with separate packages instead of one single
package, I thought it is encouraged when needed. Our old system is a 1.5
years old server which is using the legacy OOo. We are in process of
migrating the conversion server so I wanted to move to libreoffice for this
new setup.

Our old server has converted more than 100.000 files using jodconverter and
since Libreoffice comes with --convert-to argument, I also want to update
the conversion scripts to use this new native option and eliminate the
potential performance issues which come with the jodconverter. (Though we
didn't have any performance issues with the old setup since we don't convert
thousands of files daily, but native is almost always better right :))

I'll install the remaining packages to ensure the system stability. Disk
space was never an issue since we have 3 TB of space in this server,
optimisation was the main reason.

Thanks again for your help. This community is amazing. :)

David Bolen wrote

merter <serdar@> writes:

The missing package was libobasis3.5-en-us_3.5.3-2_amd64.deb. I
all these installed packages and none of them has a dependency to that
It now seems an obvious file to install but since I trusted the
system, I missed it.

I think that's because you haven't installed any of the language
packs, which is what depend on that module (it's the base module for a
given language).

There should be a top level "libreoffice3.5-en-us_xxx" package which
pulls in all the per-component language packages, including the base
one you installed manually here.  I'd probably go ahead and install
the top level package and pick up all the language packages just to be
safe, although for the most part en-us should be the same as that
built into the code.

I suppose the main packages don't want to depend on any specific
language, so selecting a language module is a top level choice (e.g.,
one of the libreoffice* packages) in and of itself.  Given that some
language pack is needed, I suppose it would be nice if the component
packages depended on a virtual language support package or something.

BTW, assuming that you are installing the debs as downloaded directly
from TDF, personally I'd just recommend installing them all and not
worrying too much about trying to cherry pick, unless you're being
really selective.  There's an awful lot of shared code among the
various components; once you're going to be including all the *core*
packages, you aren't really optimizing that much by cherry picking
beyond that.

For example, in my 3.5.4 install (direct from TDF), just the packages
you listed represent almost 80% of the space used by installing
everything.  All of the work to cherry pick only saves about 85MB of
disk space.

-- David

For unsubscribe instructions e-mail to: users+help@.libreoffice
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

View this message in context:
Sent from the Users mailing list archive at

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.