Ok ... the first hurdle is this:
Quote:
..create an automated install package for some backup agent patches.
|
One of the ideas behind RPM is that you don't patch on top, you update the package with the patch and increment the release number. When you need to update a package, you may just be adding a patch - but from the install side it always looks like an update of the application.
example spec file part:
Code:
Source0: %{name}-%{version}.tar.gz
Patch0: myapp_fix_1.patch
Example install:
So in your case the process might look like:-
- choose a host to build packages on
- configure it for building rpm's
- grab the application source rpm and install it
- edit the spec file to utilise the patch, and increment the release number
- copy the patch to SOURCES
- rebuild the rpm
And a quick guide to setting up an rpm build environment:
- 'yum -y install rpm-build rpmdevtools rpmlint'
- 'rpmdev-setuptree'
- 'cd ~/rpmbuild'
cheers