On 05/01/2018 02:12 PM, Knurpht @ openSUSE wrote:
Op dinsdag 1 mei 2018 22:37:09 CEST schreef don fisher:
On 04/28/2018 08:16 PM, don fisher wrote:
I am unable to get the F1 key to generate anything except a "not installed on your computer" message. I cannot find either under Yast or Google where to get the appropriate package to add the help files.
Thanks Don
I am now a bit afraid of contributing to this thread. I learned a lot from my interactions, sorry any dumb mistakes. But the following does work. There were comments posted about corrupting possible future upgrades, but I kept a copy of the original directory, as shown below. It is just a few directory heads that are populated by the files present in the downloaded RPM. I can reinstate the original en-US before any upgrades.
/usr/lib64/libreoffice/help/en-US/
|-- sbasic.idxl |-- scalc.idxl |-- schart.idxl |-- sdatabase.idxl |-- sdraw.idxl |-- simpress.idxl |-- smath.idxl
`-- swriter.idxl
Again, I clicked on the "libreoffice built in help" tab at the Libreoffice site: download.documentfoundation.org/libreoffice/stable/6.0.3/rpm/x86_64/Libre Off ice_6.0.3_Linux_x86-64_rpm_helppack_en-US.tar.gz which yielded an rpm: libobasis6.0-en-US-help-6.0.3.2-2.x86_64.rpm which are loaded into /opt.
I copied the files, but a symbolic link from /usr/lib64/libreoffice/help/ to /swl/libreoffice/help/ also makes the desired files available and LO help works. It was suggested that "instead of copying over files, you could create a symlink to the folder in /opt, that would make updating easier."
The error I received from Help about files not being installed was not a fatal error, so again I thought what I was doing was permissible. The /usr/lib64/libreoffice/help/en-US/en_US is at end of the tree, so I did not see where other sections would be corrupted.
I had decided to learn Libreoffice, so I thought the help would be valuable to me.
Again, Don
Good it works for you like it is now, Mind, if the packagers decide to add the help to the 42.3 packages, you might run into a conflict re. the link, if so, simply remove the link, and try the update again.
Could you please add details on the symbolic link? I thought to make a link from en_US one would first have to delete the contents of that directory. If not, wouldn't their be a redundancy between the original directory heads and those that have been populated? Again, I made a copy of the original en_US so I would have the ability to return to the original state. Is the some trick in ln -s that avoids this problem?
Thanks, Don I was speaking about the link you created, that made it work. Packages that have their own directory structure don't (always) follow symbolic links, and
Op woensdag 2 mei 2018 00:08:32 CEST schreef don fisher: the installer will report some conflict. If the packagers re-add the help files to the package, that might/will happen. In that case remove that symbolic link. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org