Yes, what you are asking to do is quite possible. One
change I suggest is to use an unpacked runtime
directory for packaging. This would allow rpm to keep
track of each installed file in your system (so rpm
-qf would work).
There are two choices to how to call rpmbuild in this
case. First method is if you wanted to use a
tar/gzipped runtime direcotry as input to rpm
packaging. Second method is if you want to just
produce rpms at the end of your build process.
For method 1:
Your spec would skip the %pre and %build step, and
would have no Source: tag.
The %install scriptlet would create $RPM_BUILD_ROOT,
and untar / unzip your runtime tree.
For %files, you can probably use just a wildcard,
assuming your build system doesn't include extraneous
files in the runtime directory.
In %clean, you would delete $RPM_BUILD_ROOT.
---
For method 2:
The build system would call rpmbuild prior to tar/gzip
of the runtime directory. You would redefine macros on
the command line to rpmbuild so that to rpm, the build
root is the same as the base of the runtime directory.
You may also need to define several other macros, but
knowing about the one will get you started.
For this case, the .spec file would not need %prep,
%build, or %install. It would just need %files and the
pre/post/preun/postun scriptlets as required. It would
also omit Source:
____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
