44< head >
55 < meta http-equiv ="Content-Type " content ="text/html; charset=us-ascii ">
66 < meta http-equiv ="Content-Style-Type " content ="text/css ">
7- < meta name ="id " content =
8- "">
97 < link rel ="STYLESHEET " href ="MakeProjectCreator.css " charset ="ISO-8859-1 "
108 type ="text/css ">
119
@@ -33,7 +31,7 @@ <h3 class="Head2">Background/Abstract</h3>
3331 workspace declarations (< samp > .mwc</ samp > files). Consequently,
3432 workspace files utilizing these new features are not
3533 backwards-compatible with prior releases of MPC.</ li >
36-
34+
3735 < li class ="body "> Since RPM is primarily Linux-based, RpmSpec only
3836 officially supports use on Linux-based systems. It < em > may</ em >
3937 work on platforms for which an RPM port exists, but such success
@@ -71,7 +69,7 @@ <h3 class="Head2">Usage</h3>
7169 Inter-project dependencies that exist between any projects known to
7270 the top-level workspace automatically turn into inter-package
7371 dependencies in RPMs.
74-
72+
7573 < h4 > Generic workflow</ h4 >
7674 < div align ="center ">
7775 < img src ="rpmworkflow.png " alt ="rpm workflow "/>
@@ -121,14 +119,14 @@ <h4><a name="mwcnotes"></a>Creating Workspaces</h4>
121119 Details on the variables allowed in the < samp > specific</ samp >
122120 clause can be found in the < a href ="../templates/rpmspec.txt ">
123121 < samp > $MPC_ROOT/docs/templates/rpmspec.txt</ samp > </ a > file.
124-
122+
125123 < p > If you use workspaces as a part of
126124 building right now, you may wish to write additional
127125 workspace files specifically for packaging via RPM.
128126
129127 < h4 > < a name ="installready "> </ a > Making Projects
130128 < em > Install-Ready</ em > </ h4 >
131-
129+
132130 MPC-assisted packaging requires some attention from the developer
133131 in order to yield its full potential. What this means is that in
134132 order for a project to avail itself to be packaged, it must take
@@ -180,7 +178,7 @@ <h4><a name="scriptnotes"></a>Notes on Generated Script</h4>
180178 architecture, instead presuming that whatever toolchain is
181179 needed can be found in the PATH or is specified in the
182180 < code > .spec</ code > file.</ li >
183-
181+
184182 < li > The script performs a build/install activity for each package.
185183 Installation is not into the running system, but rather into a
186184 "fake" area. Installation is necessary to satisfy inter-package
@@ -190,7 +188,7 @@ <h4><a name="scriptnotes"></a>Notes on Generated Script</h4>
190188 < samp > specific</ samp > clause, typically in the top-level
191189 workspace.</ li >
192190
193-
191+
194192 </ ol >
195193</ div >
196194
0 commit comments