Hi Andi B,
Currently the only way to keep dlls which are needed for ported software in a current consistent state is yum/rpm. No one offers a better way for doing this so it makes absolutely no sense to constantly ranting about. Come up with a better solution and I'm willing to discuss the pro and cons.
In actual fact it isn't. We have a policy that we have to adhere to for our clients, we can't use anything that is not approved and in the case of anything going onto the machine control computers certified. This means that we can not use RPM/YUM as I doubt it would get approval and certainly not certification.
We get round this by having either program objects that are very specific in how they start and run a program or programs are started by command files, again with very specific parameters.
At the moment I am experimenting with using a directory directly off the root of the boot drive to hold all these extraneous DLLs that is listed in the libpath of config.sys. This works and because I back it up before any additions are made it is very easy to go back to what was working if anything breaks (I have had to do this a couple of times).
Now back to Qpdfview.
Looking over the zip files of Qpdfview I find that v0.4.9 and v0.4.10 both have some of the required DLLs included while later versions do not. Also reading the README from the latest source it appears there are a number of options that can be used when building, some of which would solve some of the problems we are seeing - for instance, not everyone can get CUPS printing to work so why is it a built in requirement and must be installed for this port to work?