<div dir="ltr">Yes, the bbappend is breaking the packaging so should fix its own mess.<div><br></div><div>Ross</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 4 July 2017 at 08:36, Gordan Markuš <span dir="ltr">&lt;<a href="mailto:gordan.markus@pelagicore.com" target="_blank">gordan.markus@pelagicore.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF"><div><div class="h5">
    On 2017-07-03 15:56, Burton, Ross wrote:<br>
    <blockquote type="cite">
      
      <div dir="ltr"><br>
        <div>
          <div class="gmail_extra">
            <div class="gmail_quote">On 3 July 2017 at 13:34, Gordan
              Markuš <span dir="ltr">&lt;<a href="mailto:gordan.markus@pelagicore.com" target="_blank">gordan.markus@<wbr>pelagicore.com</a>&gt;</span> wrote:<br>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
                <div id="m_-718120503281343026gmail-:yn" class="m_-718120503281343026gmail-a3s m_-718120503281343026gmail-aXjCH m_-718120503281343026gmail-m15d087d2c6436eea">-FILES_${PN}-dev +=
                  &quot;${libdir}/cairo/*.so&quot;<br>
                  +FILES_${PN}-dev += &quot;${libdir}/cairo
                  ${libdir}/cairo/*.so&quot;<br>
                </div>
              </blockquote>
            </div>
            <br>
          </div>
          <div class="gmail_extra">I just spent five minutes working out
            *why* this fixes the QA issue you were getting.</div>
        </div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">A better fix would be to delete
          ${libdir}/cairo using:</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">  rmdir ${libdir}/cairo || :</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">or</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">  rmdir --ignore-fail-on-non-<wbr>empty
          ${libdir}/cairo</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">(former is POSIX compliant, but I can&#39;t
          think of a situation where that is only a hypothetical
          problem)</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Then in the commit message you can say
          that the directory is always created but it only has content
          if you disable cairo-trace.  At least, I hope you are
          explicitly disabling cairo-trace as there&#39;s no other way I can
          see for you go get this.</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Ross</div>
      </div>
    </blockquote></div></div>
    Thanks for the suggestion Ross, and you are right this only happens
    if there is a bbappend that removes the &#39;cairo-perf-utils&#39; package.
    An example of this is the meta-ivi layer.<br>
    Experimenting a bit it seems to me that even by adding the directory
    removal, in case it is empty, the do_package step still fails. By
    inspecting further I can observe that the directory is in fact not
    being removed but left empty which is quite puzzling.<br>
    After doing some thinking I believe it might be better to add the
    removal of the directory and the package files in the bbappend, do
    you agree with this? Here is the PR to meta-ivi that does that
    <a class="m_-718120503281343026moz-txt-link-freetext" href="https://github.com/GENIVI/meta-ivi/pull/45" target="_blank">https://github.com/GENIVI/<wbr>meta-ivi/pull/45</a>.<br>
  </div>

</blockquote></div><br></div>