Filesystem Hierarchy Standards (FHS) and certain file locations

classic Classic list List threaded Threaded
6 messages Options
Paul Menzel-2 Paul Menzel-2
Reply | Threaded
Open this post in threaded view
|

Filesystem Hierarchy Standards (FHS) and certain file locations

Dear LibreOffice folks,


Following up on bug report #100724 [1], I have two question about the
location of some files.

First, the license and README files.

```
/usr/lib/libreoffice/NOTICE
/usr/lib/libreoffice/LICENSE.html
/usr/lib/libreoffice/LICENSE.fodt
/usr/lib/libreoffice/LICENSE
/usr/lib/libreoffice/CREDITS.fodt
/usr/lib/libreoffice/readmes
/usr/lib/libreoffice/readmes/README_en-US
/usr/lib/libreoffice/readmes/README_de
```

Shouldn’t those be put under `/usr/share/doc/libreoffice/`?

Second, I wonder why the “real” binaries are put under `/usr/lib` and
not `/usr/bin/`? `/usr/lib/libreoffice/program` is normally not in a path.

```
$ ls -l /usr/bin/libreoffice
lrwxrwxrwx 1 root system 36 Sep  4 12:55 /usr/bin/libreoffice ->
/usr/lib/libreoffice/program/soffice
$ ls -l /usr/lib/libreoffice/program/
[…]
-rw-r--r-- 1 root system        50 Sep  4 12:54 redirectrc
-rwxr-xr-x 1 root system     24984 Sep  4 12:36 regmerge
-rwxr-xr-x 1 root system     13616 Sep  4 12:36 regview
drwxr-xr-x 2 root system      4096 Sep  4 12:54 resource
-rwxr-xr-x 1 root system        63 Aug 24 23:39 sbase
-rwxr-xr-x 1 root system        63 Aug 24 23:39 scalc
-rwxr-xr-x 1 root system        63 Aug 24 23:39 sdraw
-rwxr-xr-x 1 root system     13150 Aug 24 23:39 senddoc
drwxr-xr-x 2 root system      4096 Sep  4 12:55 services
-rw-r--r-- 1 root system      8690 Sep  4 12:38 services.rdb
-rw-r--r-- 1 root system        34 Sep  4 12:54 setuprc
drwxr-xr-x 2 root system        22 Sep  4 12:54 shell
-rwxr-xr-x 1 root system        66 Aug 24 23:39 simpress
-rwxr-xr-x 1 root system        63 Aug 24 23:39 smath
-rwxr-xr-x 1 root system      6051 Sep  4 12:34 soffice
-rwxr-xr-x 1 root system      7408 Sep  4 12:48 soffice.bin
-rw-r--r-- 1 root system       453 Sep  4 12:54 sofficerc
-rwxr-xr-x 1 root system        65 Aug 24 23:39 swriter
drwxr-xr-x 2 root system        42 Sep  4 12:54 types
-rw-r--r-- 1 root system     57362 Sep  4 12:36 types.rdb
-rwxr-xr-x 1 root system     41024 Sep  4 12:48 ui-previewer
-rwxr-xr-x 1 root system      1508 Aug 24 23:39 uno
-rwxr-xr-x 1 root system     99120 Sep  4 12:37 uno.bin
-rw-r--r-- 1 root system     17092 Aug 24 23:39 uno.py
-rw-r--r-- 1 root system     10956 Aug 24 23:39 unohelper.py
-rwxr-xr-x 1 root system      1390 Aug 24 23:39 unoinfo
-rwxr-xr-x 1 root system      3039 Aug 24 23:39 unopkg
-rwxr-xr-x 1 root system      7456 Sep  4 12:48 unopkg.bin
-rw-r--r-- 1 root system       239 Sep  4 12:35 unorc
-rwxr-xr-x 1 root system      7736 Sep  4 12:35 uri-encode
-rw-r--r-- 1 root system       319 Sep  4 12:54 versionrc
drwxr-xr-x 9 root system       108 Sep  4 12:54 wizards
-rwxr-xr-x 1 root system      7800 Sep  4 12:35
xid-fullscreen-on-all-monitors
-rwxr-xr-x 1 root system     60048 Sep  4 12:36 xpdfimport
```

The FHS Wikipedia article describes `/usr/lib` as below [2].

 > /usr/lib – libraries for the binaries in /usr/bin/ and /usr/sbin/.


Kind regards,

Paul


[1] https://bugs.documentfoundation.org/show_bug.cgi?id=100724
[2] https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Miklos Vajna-4 Miklos Vajna-4
Reply | Threaded
Open this post in threaded view
|

Re: Filesystem Hierarchy Standards (FHS) and certain file locations

Hi,

There are two conflicting requirements in this game. On one hand, people
want a self-contained installation set which can be unpacked anywhere,
and $instdir/program/soffice can start LO.

On the other hand, Linux distros want "system integration", where
documentation goes to /usr/share, binaries go to /usr/bin, etc.

The usual hack to resolve this conflict is that /usr/bin has symlinks to
$libdir/libreoffice/ where the installation set is stored. (Perhaps the
same is true for /usr/share.)

Regards,

Miklos

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

signature.asc (188 bytes) Download Attachment
Michael Stahl-2 Michael Stahl-2
Reply | Threaded
Open this post in threaded view
|

Re: Filesystem Hierarchy Standards (FHS) and certain file locations

In reply to this post by Paul Menzel-2
On 06.09.2017 15:55, Paul Menzel wrote:
> Following up on bug report #100724 [1], I have two question about the
> location of some files.

TDF binary packages (rpm and deb) don't install in /usr but in /opt.

apparently you are trying to use "make install", which probably is
unused and unmaintained; maybe we should remove it.

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Paul Menzel-2 Paul Menzel-2
Reply | Threaded
Open this post in threaded view
|

Re: Filesystem Hierarchy Standards (FHS) and certain file locations

Dear Michael,


On 09/06/17 16:26, Michael Stahl wrote:
> On 06.09.2017 15:55, Paul Menzel wrote:
>> Following up on bug report #100724 [1], I have two question about the
>> location of some files.
>
> TDF binary packages (rpm and deb) don't install in /usr but in /opt.

I don’t know. We don’t use binary packages.

> apparently you are trying to use "make install", which probably is
> unused and unmaintained; maybe we should remove it.

No, we use `start_cmd make -j distro-pack-install DESTDIR=/some/where`.
What do you recommend?

I don’t see a good reason to divert from standards like `./configure &&
make && make install && make check # or test`. That way, it’s one more
barrier to integrate it in continuous integration systems like Travis CI
or similar.


Kind regards,

Paul
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Eike Rathke-2 Eike Rathke-2
Reply | Threaded
Open this post in threaded view
|

make install (was: Filesystem Hierarchy Standards (FHS) and certain file locations)

In reply to this post by Michael Stahl-2
Hi Michael,

On Wednesday, 2017-09-06 16:26:09 +0200, Michael Stahl wrote:

> apparently you are trying to use "make install", which probably is
> unused and unmaintained; maybe we should remove it.

make install works fine if one configures with --prefix=..., I use it
regulary to create installations of builds and branches before I fool
around in a tree. Something like

./configure --prefix=$HOME/opt/$(basename `pwd`)

  Eike

--
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918  630B 6A6C D5B7 6563 2D3A
Care about Free Software, support the FSFE https://fsfe.org/support/?erack

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

signature.asc (849 bytes) Download Attachment
Wols Lists Wols Lists
Reply | Threaded
Open this post in threaded view
|

Re: make install

On 06/09/17 19:45, Eike Rathke wrote:

> Hi Michael,
>
> On Wednesday, 2017-09-06 16:26:09 +0200, Michael Stahl wrote:
>
>> apparently you are trying to use "make install", which probably is
>> unused and unmaintained; maybe we should remove it.
>
> make install works fine if one configures with --prefix=..., I use it
> regulary to create installations of builds and branches before I fool
> around in a tree. Something like
>
> ./configure --prefix=$HOME/opt/$(basename `pwd`)
>
And what about distros like gentoo? I don't know how portage does it,
but quite likely it uses "make install" to actually install its
applications, like libreoffice, after it's built them from source?
Portage, surely, is not supposed to use /opt?

And on another little point, aren't /usr/bin and /usr/sbin (along with
/sbin) deprecated? For some value of deprecated :-) As usual, things
move at a somewhat glacial pace, but I believe all binaries are
*supposed* to be installed or symlinked into /bin now, for the unified
root or whatever it's called.

sbin was originally meant for statically linked binaries, I believe.
Typically they were emergency rescue packages for root, hence that
transmogrifying into "packages for root" rather than "static packages".
And most of the directories in /usr being equivalents to those in /,
isn't /usr deprecated for the unified root?

Cheers,
Wol

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice