John LeMay wrote:
The issues described are not unusal or unexpected.
Ummm, ok, if you say so. This particular reported problem has never been passed along to me...hence my phrasing "what you are reporting does not sound familiar at all". Perhaps I should have appended "to me" to my original statement...
In fact, if you wrote the docs, you should reall that in the prerequisites section "kde" is clearly listed. In reality, kdelibs contains the kde-related files needed. I can't explain the OpenSSH requirements, however I would suggest adding that req to the requirements section of the documentation since it is clearly required. I may download the package myself and have a look at the spec file, but I can say for certain OpenSSH must be listed there since the install is looking for it.
I'm not sure what is happening here either -- probably a case of missing devel packages?? Those *are* required, as listed in the prereqs section of the kpsk docs: "qt and qt-devel for Qt v.3.0.3 or later, kdelibs and kdelibs-devel for KDE 3.0.1 or later, zlib-devel, libjpeg, libjpeg-devel,libpng2 and libpng2-devel" http://kpsk.sourceforge.net/kpskdocs/index.html#software
SuSE deals with RH packages pretty well, but RH packages don't always do things the "SuSE way" relative to scripts and file locations.
I guess you found an error....the spec file should not go to lemay...I'll bet that is (unfortunately) a remnant of the sample spec file included in the rpm packaging app...it was my first attempt at making rpms as well.... You could send the spec to me, but I wouldn't know what to do with it, since I don't have a working suse installation ast the moment. Thanks for working with it, though...if you care to roll the rpm for suse, I would be happy to post it for testing. 73- Ernie,kg9ni