<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-CA">Hi Cesar and build team,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">I’ve been thinking about the proposal for the unified build command as discussed in the last build team meeting. “stx --build-iso” or “stx --create-iso” was suggested as command for building all targets – source rpms,
binary rpms, and the final ISO. We should probably change that command name to “stx --build-all” or something similar. This would meet the immediate request of providing a single command to wrap around the existing steps, and would allow us to grow the tool’s
functionality without tying us to the concept of “an ISO == a build”. As a bonus, it allows us to improve the granularity the build commands while maintaining a consistent command naming convention. A potential first cut of commands could be:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"># Download items specified in lst files (replaces download_mirror.sh)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">stx --mirror-download<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"># Places downloaded items in the specified mirror path<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">stx --mirror-populate <mirror_path> <o:p>
</o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"># Do all mirror steps<o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-CA">stx --mirror-all</span></b><span lang="EN-CA"> <mirror_path><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"># sets up a build environment with artifacts from the specified mirror path (replaces generate-cgcs-centos-repo.sh and populate_downloads.sh)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">stx --build-env <mirror_path><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"># builds specified package or all packages (replaces build-pkgs)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">stx --build-pkgs [pkg_name]<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"># Produces an ISO from current build (replaces build-iso)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">stx --build-iso<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"># Runs previous steps (I’m not sure if running --build-env during build-all is a good idea, but perhaps we could skip the --build-env if no mirror_path is specified)<o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-CA">stx --build-all</span></b><span lang="EN-CA"> [mirror_path]
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Future commands like --build-patch or --sign-pkgs or --project-integrate or wherever this grows, could be added as more advanced use cases are fleshed out.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA">Jason<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>