Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I have some RPMs (a.rpm, b.rpm) then I received some new RPMs (c.rpm, d.rpm,e.rpm) but those can not be installed in same way as a.rpm or b.rpm. I have to run a script to install the new rpms.
The issue is what is the best way to run the script to install the three new rpms.
I was thinking of build another rpm x.rpm which runs the script to install c,d,e. Then I'll install a.rpm, b.rpm,x.rpm, but was told x.rpm has nested rpms and since the rpm database is locked out, it will not work.
BTW, is there some files that can specify which set of RPMs to install?
i.e. I have 100 rpms in a directory but I only want to install 5 of them, how do I specify that? in a .dsc file?
It would be useful at this point (see answers to your previous thread) to know some details about your Linux OS and the reason why you had to download 100 RPMs and install them manually. Are these RPMs coming from the official Linux distribution? Maybe did you download them from another machine, since you haven't an internet connection? Just guessing.
By the way, better to use the package manager provided out-of-the-box with your linux installation (Yast2 or zypper for OpenSuse, Add/Remove software or yum for Fedora, and so on). The reason is that it will install packages specifically built for your system and it will take care of the dependencies automatically.
It is a special set of RPMs we received from a third party and we have to use the script they provided to install those RPMs. Straight RPM installation will not work with those RPMs. This is not a nice way but we have no choice.
I do not yet know the linux distribution yet but I would like to understand a general concept of how this could be done. Of course, I can find the software process that installs the current RPMs and insert a hook to run the script we received which will install the third party RPMs. I do not feel this is a nice way, but want to seek suggestions. Initially I want to build an single RPM to run the scripts but it might not work since the RPM DB is locked out which might prevent from installing third party RPMs. I am not an expert on this.
Ok. Clear now. The script you received along with the three new RPMs could simply be a wrapper to check some dependencies and/or to perform pre- or post-installation tasks. In my opinion it would be easier to insert the installation of a.rpm, b.rpm, c.rpm, ... in the script itself, but it depends on the actual structure and aim of this script. And on the way the a.rpm, b.rpm, ... packages are going to be previously (?) installed.
Why does it matter what order they're installed in? I ask because I'm thinking it shouldn't matter.
You can make rpms depend on another rpm. So you could make c.rpm depend on a.rpm and a.rpm depend on b.rpm. That way a package manager such as zypper or yum when told to install c.rpm would automatically install a.rpm and b.rpm, assuming it could find them. Not sure that would get them installed in the order b a c though. Or you just make c.rpm depend on a.rpm and b.rpm.