Philip J. Koenig wrote: [snip]
> OK, I had tried that too, didn't see anything particularly > illuminating, but maybe you can - the output is below. > > BTW, how can I extract the files from the .rpm file manually, so I > can take a look at what it's looking for, etc? I don't see an rpm > command to do that, and midnight commander's rpm "virtual filesystem" > doesn't seem to 'see' those kinds of things. $ rpm -q your.rpm --scripts might help. The "alien" and "rpm2tgz" packages allow to you dissect RPMs soemwhat. You can also use rpm2cpio to extract the cpio archive, and then use cpio to unpack the RPM. > One other thing: kpackage from wkstn 3.1 seems to reliably crash if I > open an rpm file and then try clicking on it in the left-hand > "PACKAGES" window after it's been opened. (therefore the right-hand > panel is always empty) Perchance not to use kpackage, then? > D: Signature size: 149 > D: Signature pad : 3 > D: sigsize : 152 > D: Header + Archive: 644097 > D: expected size : 644097 > D: opening database mode 0x0 in /var/lib/rpm > D: found 0 source and 1 binary packages > D: YES A perl = 5.6.0-4 B perl = 5.6.0 > D: requires: perl = 5.6.0 satisfied by db packages. > D: requires: /etc/cron.d unsatisfied. Hmm. install's -d option will force the creation of the desired directory. I'm guessing the Makefile has something hardcoded that's causing this to break. Kurt -- "Little else matters than to write good code." -- Karl Lehenbauer _______________________________________________ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
