Bug 78341 - Cannot install document templates to architecture-independent location
Summary: Cannot install document templates to architecture-independent location
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Installer
  Show dependency treegraph
 
Reported: 2014-05-06 13:59 UTC by David Woodhouse
Modified: 2020-03-14 11:46 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Woodhouse 2014-05-06 13:59:38 UTC
I would like to create an RPM package for our company's Fedora users which contains a bunch of company document templates.

It looks like these need to live in /usr/lib64/libreoffice/share/ or /usr/lib/libreoffice/share/ depending on whether it's a 64-bit or 32-bit platform. Therefore I can't build an architecture-independent package; I have to build architecture-specific packages. With identical content.

This makes me sad, and I think it probably violates the FHS. Isn't there a place in /usr/share that I can put templates in? If not, please *could* there be?

cf. http://bugzilla.redhat.com/1092570
Comment 1 Cor Nouws 2014-05-18 15:14:10 UTC
Hi David,

One can add templates in an extension.
And adding that extension unpacked in the folder 
   libreofficeshare/extensions/
will ensure that the templates are available.

HTH,
Cor
Comment 2 Cor Nouws 2014-05-18 15:15:26 UTC
(In reply to comment #1)
>    libreofficeshare/extensions/

   libreoffice/share/extensions/ of course
Comment 3 David Tardon 2014-05-19 07:16:51 UTC
(In reply to comment #1)
> Hi David,
> 
> One can add templates in an extension.
> And adding that extension unpacked in the folder 
>    libreofficeshare/extensions/
> will ensure that the templates are available.

Hi Cor,

you are missing the point here. The problem is that libreoffice/share/extensions _itself_ is in an architecture-dependent location in distribution builds. E.g., on Fedora, it is /usr/lib/libreoffice/share/extensions for 32-bit arch and /usr/lib64/libreoffice/share/extensions for 64-bit arch. That means that if one packages some templates (or a gallery, or a java extension, FWIW), one cannot make the rpm "noarch". Instead, one has to build it for all arches, even if it is no actual need for that. This request is for real arch-independent extension dir, e.g., /usr/share/libreoffice/extensions .
Comment 4 Cor Nouws 2014-06-22 14:30:15 UTC
Hi David,

(In reply to comment #3)

> you are missing the point here. The problem is that
> libreoffice/share/extensions _itself_ is in an architecture-dependent
> location in distribution builds. E.g., on Fedora, it is
> /usr/lib/libreoffice/share/extensions for 32-bit arch and

Sorry for being toooo short in my comment.
I meant <install>/libreoffice/share/extensions/ 
so that is in the package. Does that help?
Comment 5 David Tardon 2014-06-23 06:30:31 UTC
(In reply to comment #4)
> Hi David,
> 
> (In reply to comment #3)
> 
> > you are missing the point here. The problem is that
> > libreoffice/share/extensions _itself_ is in an architecture-dependent
> > location in distribution builds. E.g., on Fedora, it is
> > /usr/lib/libreoffice/share/extensions for 32-bit arch and
> 
> Sorry for being toooo short in my comment.
> I meant <install>/libreoffice/share/extensions/ 
> so that is in the package. Does that help?

You are still missing the point :-) It is not a problem to get the path to install the extension into on different platforms. The problem is that I have to build a separate package for every platform, even if there is nothing platform-dependent in the extension itself! There is no other way, as files in /usr/lib* are considered platform-dependent. Platform-independent data packages would normally go somewhere into /usr/share. But there is no possibility for that in libreoffice.
Comment 6 Orion Poplawski 2014-10-28 16:44:28 UTC
Yes, we really need to have libreoffice look in /usr/share/libreoffice for architecture content, and libreoffice itself should install architecure independent content there.  We are discussion this in packaging guidelines for Fedora here https://fedorahosted.org/fpc/ticket/465 and this is a concern.
Comment 7 Joel Madero 2014-11-06 22:51:10 UTC
Moving this to NEW as DTardon is involved and knows what's up (I think :) ). Thanks all.
Comment 8 Cor Nouws 2014-11-07 13:15:13 UTC
Still, when you deploy an .oxt as admin, you can place it in the programs path. So the same extension (.oxt) applies to all platforms..
That's what we use in e.g. LibreLex
Comment 9 QA Administrators 2015-12-20 16:18:38 UTC Comment hidden (obsolete)
Comment 10 David Woodhouse 2015-12-20 16:50:08 UTC
(In reply to QA Administrators from comment #9)
> Please DO NOT
> Update the version field
...
> 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 

Well, it's assume that "setting" the version field as instructed is not the same as "updating" the version field, and do so despite the otherwise contradictory instructions.

This is still an issue in current versions, it seems.
Comment 11 QA Administrators 2017-01-03 19:50:09 UTC Comment hidden (obsolete)
Comment 12 Buovjaga 2020-03-14 11:46:10 UTC
Alessandro-B in IRC confirmed this for 6.3.5 at least.