Comment 2 for bug 1879168

Revision history for this message
mj162 (mj162) wrote :

Adam, many thanks for an amazingly fast and helpful response.

Unfortunately building is not an option. The thin clients are
essentially appliances into which a USB stick of pre-packed apps are
inserted into. (They're probably unsuitable for development, anyway).

Thanks. I tried various settings of QPDFVIEW_PLUGIN_PATH without
success -- perhaps the version Canonical have in their repository
for V16.04 is just too old to support it.

As you say, since I am copying things about, moving the plugins is not
an issue. I just need to leave notes so that when there is a new
version, the procedure to modify where the components of the package are
deployed-to is followed.

When you say move the plugins to the directory the binary is in, I have
a question if I may please.

The plugins are in:

/media/GenericFlash_sdb1/usr/lib/x86_64-linux-gnu/qt5/plugins

But there are many plugins in subdirectories under there that will be
in-use by other packages.

Do I take that you were referring strictly to the sqldrivers plugins,
and that it is these that I should move/copy to the directory of the
binary? (and, if so, place the contents of sqldrivers in the same
directory as the binary, or place the sqldrivers directory within the
same directory containing the binary?)

Or have I misunderstood and that the solution you are proposing is to
move/copy the contents of qpdfview supplied libraries, for me, currently
in:

/media/GenericFlash_sdb1/usr/lib/qpldfview

Into the same directory as the binary?

Sorry for coming back at you, having tried the env variables, I just
wanted to make sure I understood the moving files solution correctly.

Thank you and stay safe.

Kind regards.