Hi,
This is my first
post to the list, though I've been lurking for a few days.
I have been reading
Maximun RPM and a host of other howtos and I've got a .spec file in
progress, but I'm confused about how to do something that appears to not fit so
neatly into the documentation I've read.
The challenge is
this:
We have our own
build process that creates all the necessary object files on each of our UNIX
platforms (there are three, and AIX and Linux are the two I'm interested in
delivering via RPM). We cannot ship our sources to our customers, yet we would
like to leverage the RPM database to track and manage what files get installed
at the customer site.
We have a packaging
process that follows compilation which plucks all of the objects and library
dependencies into a "runtime" directory that represents what the customer will
have installed. This "runtime" directory is tarred up and gzipped and this is
what we deliver to the customer as a release, also shipping a set of scripts
alongside that handle the gunzipping and untarring of the deliverable, the
creation of logdirs, the setup of config files and the tweaking of system
settings necessary for getting things to run.
What I want to do is
to create an RPM that contains what I've compiled in the form of the gzipped tar
I create, and also encapsulates the scripting necessary to untar, create dirs,
setup configs and tweak settings in the .spec file.
I'm stymied, though,
as to how to use the rpmbuild dirs to achieve this. Which ones should I not use,
if I'm not having the customer compile the code as a part of RPM installation?
What steps in the .spec file can I skip? Do I get any advantage out of not
pre-tarring-and-gzipping my build products? Which steps in the .spec
file must I certainly use to contain my scripting?
I've had a lot of
experience with solaris packaging, so I understand preinstall, install,
postinstall ... and preun, un and postun. Rpmbuild has got a lot more
complexity, though, and appears to be more suited to open source deliveries than
the kind of closed-source installs I'm trying to achieve.
I'd appreciate some
advice, and some help getting started.
Thanks,
--
R
Randy Novick
Software Configuration Management
McKesson Provider Technologies
randy.novick@xxxxxxxxxxxx
(303) 926-2229
Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
