> > On Wed, 12 Jun 2002, Joseph V Moss wrote: > > > > > There's one more thing you should look at when examining an RPM to see what > > it's going to install on your system: the install scripts. > > > > rpm -q --scripts somerpm.arch.rpm > > > > should let you see what changes the rpm will make besides just installing new > > files. > > Thanks, but for some reason there seems to be a constituency of people > out there who can't get over the idea that I'm not installing anything > on my system this way.
I understand what you want and for 99% of RPMs, using rpm2cpio to extract the embedded cpio archive of files will get you what you want. I'm just saying that you better not ignore the scripts. In some (a few) RPMs they represent much more of a payload (and, in some cases, may even create more files) than the cpio archive contents. In theory, you could have an RPM where 'rpm2cpio foo.rpm | cpio -idm' would give you nothing but a simple README file, but 'rpm -i foo.rpm' would install 30 files on your system. Wouldn't you like to examine those other 29 files too? Then look at the script that generates them. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
