[Libreoffice] What do we want from extensions module?

Matúš Kukan <matus.kukan -AT- gmail.com>
Wed, 14 Dec 2011 12:34:48 +0100

Hi,

I'm going to have a look at converting extensions to gbuild.
But I'd like to avoid converting unused things and extensions look old.

I think at least source/config/ldap and source/xmlextract are not used.
I was searching for service strings from ldapbe2.component and
xmx.component. Is this enough ? Can I delete the directories?

Probably the rest is used and we want to build it?

Best,

Matus

Context

[Libreoffice] What do we want from extensions module? · Matúš Kukan
- Re: [Libreoffice] What do we want from extensions module? · Michael Meeks
  - Re: [Libreoffice] What do we want from extensions module? · Bjoern Michaelsen
  - Re: [Libreoffice] What do we want from extensions module? · Stephan Bergmann
- Re: [Libreoffice] What do we want from extensions module? · Michael Stahl
  - (message not available)
    - Re: [Libreoffice] What do we want from extensions module? · Michael Stahl
      - Re: [Libreoffice] What do we want from extensions module? · Peter Foley
      - Re: [Libreoffice] What do we want from extensions module? · Christian Lohmaier
        
        [Libreoffice] dyld install_name: Re: What do we want from extensions module? · Michael Stahl
      - Re: [Libreoffice] What do we want from extensions module? · Michael Meeks
      - Re: [Libreoffice] What do we want from extensions module? · Matúš Kukan

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.