RPM Packaging For The Masses, Part 1+2

[Tommy Reynolds]

Hello,

As I review Paul's excellent RPM packaging tools, it seems we could
be giving the doc authors a head start in replacing the embedded
<articleinfo> and <bookinfo> elements with the "rpm-info.xml" file,
from which we derive everything needed to build the RPM's and keep
all the author/revision information consistent.

Two steps will be required to get all this working for the masses:

1) Authors must replace the <articleinfo> or <bookinfo> with a separate
"rpm-info.xml" file; and

2) "docs-common/Makefile.common" must be updated with the RPM rules.

I have the example-tutorial and the docs-common/Makefile.common ready
to check-in and thus require that each document have a
"fdp-info-${LANG}.xml" file before the document will build.  I've
already checked in a "docs-common/bin/db2rpm-info" script to make
extracting the "rpm-info.xml" file data as simple as possible.

This seems to be a natural checkpoint before moving on to working on
the RPM packaging stuff.  Getting the RPM rules packaged properly
could take a few more days, and doc authors could be busily cranking
out the "rpm-info.xml" files.

Question: should I: a) go ahead a check in the "rpm-info.xml" changes,
along with a message to the list; or b) wait until all the RPM
infrastructure is ready and do it all in one fell swoop?

I'd prefer to a) go ahead now.  Paul or I should do a quick HOW-TO
about what goes into the "rpm-info.xml" file so that would be
available concurrently with step (a).  

Pay me now, or pay me later ;-)

Comments?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-dsco-list/attachments/20060106/06b52e7c/attachment.sig>