....
I have tried including the files:
libQt5Pas.so
libQt5Pas.so.1
libQt5Pas.so.1.2
libQt5Pas.so.1.2.6
No, that will not work Graham, Linux and Unix puts a lot of effort into managing shared libraries, there are predefined places where libraries end up and apps do not look elsewhere for them. There are ways around that but they attack the very meaning of Unix.
If you have a script that is doing your install, you can include a line in that script that does an "official" install, "sudo apt install libqt5pas", the person running the install will be asked to put in their password and it will work. However, as I mentioned above, Linux users are generally quite happy to run that command themselves. In fact, sensible one will feel a lot safer, there is a risk associated with responding to an unknown script that asks for your password. You feel a lot safer issuing a specific command that you know will ask for your password.
My suggestion is you have the end user run your install script and at the end of it, you have a line along the lines of
echo "OK, app is installed, now you must type in and run the following command (you will be asked for root password) "
echo " sudo apt install libqt5pas [enter]"
That approach gives you a chance to test to see if qt5pas is already installed, and to see which flavour of linux it is so you can adjust the command line, different Linuxes use different installers AND even different names for the library.
There a number of different tutorials about how to make a deb, but none are really suitable for beginners.
There are two basic sorts, a binary deb and a source deb. If you want to distribute the app via the various Linux Repos,it has to be a src deb and thats massively hard. But a binary deb is much easier, especially if you are happy to ignore some of the warnings that will almost certainly be generated.
The idea is to build a directory that has files located in equivalent to the final places they need end up in. Then run tool that bundles it up into a deb, you need to conform to the rules about where things go but not absolutely. Everything is installed in root space, nothing in user space. So, you build that directory, somewhere down in your own space and the tool looks at it, bundles things up, and finally creates the deb file.
There is also a 'control' file that specifies meta data about the package, things like dependencies (ie libqt5pas) and where you want menu entries to appear etc.
I build both binary packages and src packages for my app, please look at
https://github.com/tomboy-notes/tomboy-ng/blob/master/package/package.bash, particularly, the function, DebianPackage () for an example of how to build a binary package. The script is quite long because it does a whole lot of other packaging things as well.
Davo