<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=utf-8">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Managing the rpm dependency tree in an automated way is one of the key things I’m hoping we can learn from (leverage) from the Clear Linux project. They seem to have solved this problem. Several ex-Clear team
members are on our team now and thinking about this…<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> brucej<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><a name="_____replyseparator"></a><b><span style="color:windowtext">From:</span></b><span style="color:windowtext"> Scott Little [mailto:scott.little@windriver.com]
<br>
<b>Sent:</b> Friday, July 20, 2018 6:48 AM<br>
<b>To:</b> Hu, Yong <yong.hu@intel.com>; starlingx-discuss@lists.starlingx.io<br>
<b>Subject:</b> Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">erlang*18.3.4.4*rpm are the ones to use. The R16B version should have been excluded.<br>
<br>
<br>
Yes, our mirror was of all ~30000 rpms. In this way, when a designer adds a new package or dependency, it and it's recursive dependencies were already present and ready for use.
<br>
<br>
The method that has been concocted for StarlingX requires adding packages to .lst files every time there is a change. Further there doesn't seem to be a tool to assist in the search for missing dependencies. The result is likely to be several iterations of
... <br>
<br>
add package, compile, fail due to missing dependency, <br>
add package, compile, fail due to missing dependency ...<br>
<br>
very time consuming and frustrating.<br>
<br>
<br>
Scott<br>
<br>
<br>
On 18-07-19 09:00 PM, Hu, Yong wrote:<span style="font-size:12.0pt"><o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi Scott,<o:p></o:p></p>
<p class="MsoNormal">I noticed in the black_list, there are a couple of RPMs (such as erlang*-R16B*.rpm”), which were in tis-r4-CentOS mirror but were NOT used since tis-r5-CentOS.<o:p></o:p></p>
<p class="MsoNormal">As well, we are certain they are not needed for building R5 or current StarlingX codebase.<o:p></o:p></p>
<p class="MsoNormal">Could we just drop them?<o:p></o:p></p>
<p class="MsoNormal">BTW: in tis-r5-CentOS mirror, there are over 30,000 RPMs, while actually among those only ~1900 RPMs are necessary.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">regards,<o:p></o:p></p>
<p class="MsoNormal">Yong<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">Scott Little
<a href="mailto:scott.little@windriver.com"><scott.little@windriver.com></a><br>
<b>Date: </b>Wednesday, 18 July 2018 at 11:17 PM<br>
<b>To: </b><a href="mailto:starlingx-discuss@lists.starlingx.io">"starlingx-discuss@lists.starlingx.io"</a>
<a href="mailto:starlingx-discuss@lists.starlingx.io"><starlingx-discuss@lists.starlingx.io></a><br>
<b>Subject: </b>Re: [Starlingx-discuss] StarlingX.repo using CentOS 7.3 binary repos instead of 7.4?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a name="_MailOriginalBody">StarlingX should be based on Centos 7.4 for the vast majority of packages. I think there are a dozen that have made the move to 7.5. There are also a few that we blacklisted and are pulling from earlier releases.<br>
<br>
I'll attach my black_list notes as they exist today. I'll have to audit them to make sure my notes are up to date.<br>
<br>
Scott<br>
<br>
<br>
<br>
<br>
On 18-07-18 10:47 AM, Penney, Don wrote:<o:p></o:p></a></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The StarlingX.repo file in stx-tools has all the CentOS 7.4.1708 binary repos disabled and is instead using 7.3.1611. This would likely explain why some of the specified RPMs cannot be downloaded via yum, as they were upversioned in 7.4.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Was this done for a particular reason, or is it a configuration error?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333">Don Penney</span></b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333">, Developer,
</span><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#CC0000">Wind River</span></b><br>
<br>
<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Starlingx-discuss mailing list<o:p></o:p></pre>
<pre><a href="mailto:Starlingx-discuss@lists.starlingx.io">Starlingx-discuss@lists.starlingx.io</a><o:p></o:p></pre>
<pre><a href="http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a><o:p></o:p></pre>
</blockquote>
<p> <o:p></o:p></p>
</blockquote>
<p><o:p> </o:p></p>
</div>
</body>
</html>