Alright, I've been playing around with SuSE lately and need to figure out how to deal with all this rpm crud.
There is a package I need to customize. So what do I need to do to create a fully functional RPM that will replace the current package that I need to compile with some custom options. However it is a commonly used package and I need to make sure that it remains as identicle to the original version as I can get it so I don't break the gazillion different packages that depend on it.
So I figure I need to get the pristine source code for the package and the spec file. Then I can modify the spec file with my custom options and build the replacement rpm and then "upgrade" it into the system.
Seems pretty straight forward. The problem is, how exactly do I do this? Is their a way to rip the spec file out of a existing RPM file? Or is it kept somewhere else so that I will have to track down the original developer or something for it?
There is a package I need to customize. So what do I need to do to create a fully functional RPM that will replace the current package that I need to compile with some custom options. However it is a commonly used package and I need to make sure that it remains as identicle to the original version as I can get it so I don't break the gazillion different packages that depend on it.
So I figure I need to get the pristine source code for the package and the spec file. Then I can modify the spec file with my custom options and build the replacement rpm and then "upgrade" it into the system.
Seems pretty straight forward. The problem is, how exactly do I do this? Is their a way to rip the spec file out of a existing RPM file? Or is it kept somewhere else so that I will have to track down the original developer or something for it?
