@@ -556,22 +556,24 @@ <H3><A name="15">15</A>) How are RPM's packaged?</H3>
556556 paradigm. 'How is the RPM built?' is a multifaceted question. The
557557 obvious simple answer is that I maintain:</ P >
558558
559- < P > 1.) A set of patches to make certain portions of the source tree
560- 'behave' in the different environment of the RPMset;</ P >
559+ < OL >
560+ < LI > A set of patches to make certain portions of the source tree
561+ 'behave' in the different environment of the RPMset;</ LI >
561562
562- < P > 2.) The initscript;</ P >
563+ < LI > 2.) The initscript;</ LI >
563564
564- < P > 3.) Any other ancilliary scripts and files;</ P >
565+ < LI > 3.) Any other ancilliary scripts and files;</ LI >
565566
566- < P > 4.) A README.rpm-dist document that tries to adequately document
567+ < LI > 4.) A README.rpm-dist document that tries to adequately document
567568 both the differences between the RPM build and the WHY of the
568569 differences, as well as useful RPM environment operations (like,
569570 using syslog, upgrading, getting postmaster to start at OS boot,
570- etc);</ P >
571-
572- < P > 5.) The spec file that throws it all together. This is not a
573- trivial undertaking in a package of this size.</ P >
571+ etc);</ LI >
574572
573+ < LI > 5.) The spec file that throws it all together. This is not a
574+ trivial undertaking in a package of this size.</ LI >
575+ </ OL >
576+
575577< P > I then download and build on as many different canonical
576578 distributions as I can -- currently I am able to build on Red Hat
577579 6.2, 7.0, and 7.1 on my personal hardware. Occasionally I receive