Hi rhtoras,
You've asked about how to resolve dependencies on applications you obtain via links from https://pkgs.org/. But even before you begin that process you should consider the factors discussed on this post, viewtopic.php?p=2952#p2952
That post provides links to the PaDS application and how I use it to build applications. While the latter involved building an application using Ubuntu binary packages and dependencies, PaDS will also work with Slackware binary packages and dependencies. To some extent it also discusses making use of pkgs.org.
There's another application I find useful; and more germane to your question especially when your source for packages is pkgs.org: ListDD (List Dynamic Dependencies. It may already be builtin to Quickpup64. Look on the Utilities Menu. If not, you can obtain it here, http://www.smokey01.com/radky.
When you type the name of an application into pkgs.org's Search box, select a distro-version, then follow the links to the application's binary's link, that web-page will provide a list of the binary's dependencies. For example, searching "xfe", selecting Fedora x86-64, got me here, https://fedora.pkgs.org/rawhide/fedora- ... 4.rpm.html. Scrolling down, before you reach the Download links to binaries Section, you'll find the "Requires" list.
The most important information, if it appears on that list, is a designation of the minimum GLIBC required. For the above among the "Requires" is "libc.so.6(GLIBC_2.34)(64bit)". There's a good chance that Puppy has builtin most of the required libraries. Others can be downloaded and if necessary a symbolic link created; e.g. FILE.so.14 required, but you could only find File.so.15. You create a symbolic link named File.so.14 which points to File.so.15. But, currently, a Puppy can only have one GLIBC frame-work and if yours is below the minimum required you're not going to be able to construct a functioning application with that binary. Perhaps look for an older version.
Beyond noting any GLIBC limitations, and python dependencies, you can initially ignore dependencies. Just download the binary and, rather than install it, extract it such as via UExtract. viewtopic.php?f=106&t=594&hilit=UExtract. Then file-browse to it, Right-Click it and select ListDD from the pop-up menu. One of the bottom tabs of the ListDD GUI is named “Missing”. It will generate a report of any dependency not already on your system. Unfortunately, ListDD does not provide information regarding python modules.
If no dependencies are missing, you can just install the package. But if some are I distinguish between Qt/Qt5 and others. Many applications make use of Qt/Qt5. Those I'll either install right away, or store somewhere to later be included in a pet of all additional 'frame-work' libraries I'll want on my system. If PPM doesn't provide them, pkgs.org almost always will.
After hunting down and downloading all the then known missing dependencies, I'll place them along with the application's binary in a uniquely named folder. As in the Example post I referenced above --where Ubuntu repos were the source of packages-- I can Right-Click that folder and select PaDS's 'Combine to SFS' facility. This will create an SFS you can SFS-Load to examine further. But it creates that SFS in /root. Move it before testing because (a) while in /root it occupies RAM and (b) if you SFS-Unload it from there it will be deleted.
Unfortunately, testing by first creating an SFS doesn't work with python applications. In Puppy's 'merge-file-system' application SFSes have lower priority than files either builtin or installed. Puppy will default to using higher priority python modules rather than those included in an application SFS. The only way to test is to build a pet, install it and run it via a terminal, examining the terminal output for problems.
You can still use PaDS to combine many packages as an intermediate step in creating a pet. Create an SFS, then Left-Click it. Select view. Then copy all the files in the window which opens into another uniquely named folder. Right-Click that folder and Select 'Create a pet' or open a terminal and type dir2pet NAME-OF-FOLDER.
I do strongly suggest that before installing anything you back up your SaveFile/Folder. SFSes are not installed so can be tested without endangering your current system.
There is another application which you should be aware of. Pkg-Cli. https://oldforum.puppylinux.com/viewtop ... 41#p985531. I'll let someone who actually knows how to use it provide instructions. It may be a better option especially when python is involved.
