How to extract spec file from rpm file

nayankk · 03-21-2006, 03:29 AM

Hi all,

Is there any way to extract the spec file from rpm package(not *.src.rpm)?

Thanks

unSpawn · 03-21-2006, 03:55 AM

A .spec is similar to a Makefile. When you install an application from tarball it (usually) doesnt automagically install the Makefile. When you make a rpm from spec it doesnt include the spec file. So, no there isnt any way. Any reason why you would need that?

acid_kewpie · 03-21-2006, 03:59 AM

If the espec file is held within the compiled rpm, which, along with UnSpawn, i don't think it is, then you can enter an rpm archive using tools like mc, and copy out arbitrary files of interest.

nayankk · 03-22-2006, 01:16 AM

I want to extract the depends field of rpm package. When i give rpm -q --requires, it gives depends information in the form of capabilities.
For example,

Code:

#rpm -q --requires xmms

arts-devel >= 1.0.1
gtk+-devel  
esound-devel  
mikmod  
/usr/bin/automake-1.4  
/usr/bin/autoconf-2.13  
rpmlib(CompressedFileNames) <= 3.0.4-1

I want to get these information in terms of package names (as in debian) and not in terms of capabilities. Is there any way to do so?. I thought i could get these information from spec file.

Thanks.

unSpawn · 03-22-2006, 06:00 AM

I want to get these information in terms of package names (as in debian) and not in terms of capabilities. Is there any way to do so?
What you could do after you -q --requires is resolve capabilities to filenames, then query the rpm db for the package the filenames are in (using queryformat tag for names). Since rpm doesn't need to resolve capabilities like you want to, depending on how you resolve capabilities it will either be rather CPU/IO intensive or less accurate.

acid_kewpie · 03-22-2006, 07:23 AM

coulda sworn i hit reply when i typed a response earlier....

anyway... just use the -p option to show what the dependencies of an actual rpm file are, irrespective of the state of rpm database on your system

unSpawn · 03-22-2006, 07:55 AM

just use the -p option to show what the dependencies of an actual rpm file are
You sure? On my boxen only thing "-p" does is select a rpm that wasn't installed.

acid_kewpie · 03-22-2006, 09:26 AM

-p is package, so "rpm -qpl blah.rpm" shows the contents of the blah.rpm file, as opposed to the file list dug out of the rpm db in the case of a normal already installed package.

unSpawn · 03-22-2006, 05:24 PM

-p is package, so "rpm -qpl blah.rpm" shows the contents of the blah.rpm file
But thats got no bearing on the whole finding dependencies thing, innit?

acid_kewpie · 03-23-2006, 01:11 AM

Code:

[root@kermit ~]# rpm -qp --requires  rdesktop-1.4.1-0.2.el4.test.i386.rpm
libX11.so.6
libc.so.6
libc.so.6(GLIBC_2.0)
libc.so.6(GLIBC_2.1)
libc.so.6(GLIBC_2.2.3)
libc.so.6(GLIBC_2.3)
libcrypto.so.4
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1

unSpawn · 03-23-2006, 08:34 AM

Like I said. Only the ability to select not installed packages.

kumkee · 10-12-2007, 07:24 PM

You can extract the spec file from a source rpm file (some times a binary rpm file), using command:

rpm2cpio {FullNameOfRPM} | cpio -iumd {NameOfRPM.spec}

Ramanan · 03-10-2009, 02:09 AM

This doesn't help to find out the script that rpm run during and after copying files.
Is there any way to find that ?

Quote:

Originally Posted by kumkee

You can extract the spec file from a source rpm file (some times a binary rpm file), using command:

rpm2cpio {FullNameOfRPM} | cpio -iumd {NameOfRPM.spec}

PeterKittReilly · 11-11-2009, 09:30 AM

Probably too late, but the way to see a spec file in an rpm file is
rpm --scripts -qp my-great-app-1.1.2.rpm

gnashley · 11-11-2009, 01:11 PM

Binary rpm archives *do* contain the spec file -it's written into the header of the archive. rpm needs them so that it can extract any postinst scripts etc which are needed for the package. If you open an rpm in a hex editor you can see the text contents of the spec file close to the top.