Ivan -
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?
I can only speculate on this -
- maybe the majority of users who read pdfs have sometimes the need to print part or whole pdf (like me)
- maybe the creator team of this program decided that they need to print sometimes and they decided the way to go is cups
- maybe the porter of this application does follow the above arguments or simply did not see any sense in cutting out code he ported from the qpdfview project (and increasing his own workload considerable) only to make one OS/2 user happy while distress a lot of others
Of course you can ask on qpdfview user or developer list this topic. But for me such discussions are as useless as a hole in the head. And fear the developers of qpdfview will see it similar. They use some *nix system where cups is standard. If I should speculate again they will say that's the way it is, take it or leave it.
which is not the answer for cleaning up old dlls. 'which -lasu libc065.dll' can only find dlls in current directory and libpath. But not the ones which are loaded by some application in theirs directory regardless if you have . in libpath or not. Btw. that's the reason why I implemented in my which port a warning message about that fact. And that's why I wrote above -
What a user needs to do for cleaning up his mess would be searching all drives for duplicates of every dll in %unixroot%/usr/lib. Tools like DataSeeker, pmseek, SearchPlus can be used for this.
Problem is too many users copied some dlls into some directories all over their system and now reap what they sow. Ways to start cleaning of a system are
- run one of the above tools at least for all dlls and dependencies listed in the readme
- double check with which -lasu all these dlls (you can use pmdll to get the list of dlls but you have to repeat this step)
- check all your programs you start automatically or manually after reboot for dlls they use and where they are placed on your system
Another method would be reinstalling eCS WITHOUT manually changing libpath afterwards (I hate to suggest the Windoze way)