Re: [Libreoffice] Problem using bin/ooinstall -l <target directory>

Caolán McNamara <caolanm -AT- redhat.com>
Mon, 11 Oct 2010 09:08:20 +0100

On Mon, 2010-10-11 at 08:22 +0200, Giuseppe Castagno wrote:

LeMoyne wrote:

 an idea... tmp target path has no-name directory or extra slash (//) marked
with *** here: 

... LibreOffice/***/gid_Starregistry_Services_Rdb_servicesrdb ...


hmm, I don't know.
It seems to me rather something related to a LibO API service being 
registered and failing. Something related to the e-mail service.
But I don't understand what and why.


There seems to be a problem with the installer on e.g. Ubuntu for python
components. As a hackaround adding --with-system-python to
the ./autogen.sh line might work. I'm not seeing the problem on e.g.
Fedora, but I've heard the complaint a few time so far.

C.

Context

[Libreoffice] Problem using bin/ooinstall -l <target directory> · Giuseppe Castagno
- Re: [Libreoffice] Problem using bin/ooinstall -l <target directory> · LeMoyne
  - Re: [Libreoffice] Problem using bin/ooinstall -l <target directory> · Giuseppe Castagno
    - Re: [Libreoffice] Problem using bin/ooinstall -l <target directory> · Caolán McNamara
      - Re: [Libreoffice] Problem using bin/ooinstall -l <target directory> · Giuseppe Castagno
      - Re: [Libreoffice] Problem using bin/ooinstall -l <target directory> · Laurent Godard
- Re: [Libreoffice] Problem using bin/ooinstall -l <target directory> · Michael Meeks
  - Re: [Libreoffice] Problem using bin/ooinstall -l <target directory> · Giuseppe Castagno

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.