ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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?
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.
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.