apparently the ability to create RPMs from scratch, as opposed to using an already built (needing to be compiled) src.rpm, is a magical task.
I know I am not the first nor the only person to ever have to do this, but nobody seems to know how to build an RPM from scratch... well, almost nobody.
I found the following links that provide some details and might be helpful to someone else to get caught up to the same level of competency as myself (which I know is not saying too much):
Youtube Links to get started:
The Urban Penguin - https://www.youtube.com/watch?v=364Plv6 ... 80KjLIGRKE
Philippe Loctaux - https://www.youtube.com/watch?v=CVCIUQ1 ... 80KjLIGRKE
Edureka! - https://www.youtube.com/watch?v=TINRpzM ... 80KjLIGRKE
TheCentOSProject - https://www.youtube.com/watch?v=CTTbu_q ... 80KjLIGRKE
Manoj Jaswat - https://www.youtube.com/watch?v=otL3NU2 ... 80KjLIGRKE
RocketWolf - https://www.youtube.com/watch?v=4J_Iksu ... 80KjLIGRKE
Fedora Page for in-depth information:
Fedora Quick Docs | Creating RPM Packages - https://docs.fedoraproject.org/quick-do ... kages.html
I still have some questions though.
- 1. I am building an RPM from scratch for the NVIDIA Drivers for a specific video card. I download their (NVIDIA's) .run file and execute to get the binaries, docs, and libraries all into place. Some of the libraries are actually linked from one path to the other. How do I ensure that the RPM delivers the files and their associated links?
- 2. Also, how do I control the run-level state of the machine during the time the drivers are installed? I need to bring the machine down to runlevel 3 (for RHEL6) and the equivalent for RHEL7, drop in the drivers, docs, and libraries, then REBOOT the machine (that's what I want done anyway).