View Single Post
Old 02-10-2019, 04:00 PM   #11
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 27,553
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Things are a bit of a mess on PCLOS. In choosing to support two different--specific--versions of libhunspell (v1.3 and v1.6), they've eliminated the possibility of a python script being able to accurately find the hunspell shared library it needs to find. Never mind the /usr/share/share/sigil weirdness.

Most distros have a libhunspell.so link that will point to whichever version the system has chosen as the default. PCLOS apparently has no default version of libhunspell. So Sigil's python plugin framework can't easily guess which version it needs to be looking for.

Not sure what the way forward is there for future Sigil support on PCLOS. We may have to create an environment variable that can be used to set the hunspell version at runtime so we can work around these fringe issues.

The good news is that not a ton of plugins out there are using the hunspell interface. You may be able to do without.

Or in the meantime, one workaround is to create a symbolic link in /usr/lib/sigil named libhunspell.so that points to /usr/lib64/libhunspell-1.6.so.0.0.1. That will work until they decide to move to hunspell v1.7.
DiapDealer is offline   Reply With Quote