<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 02/26/2018 02:35 AM, Burton, Ross
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJTo0LaHk+CcKw_ayGWD0n=ycqnCLewx4F531Y5MTvn-OnOoVw@mail.gmail.com">
      <div dir="ltr">Well, maintainers.inc is oe-core specific until we
        have a way to tell bitbake "include every
        conf/include/maintainers.inc you can find", but if that existed
        then it's definitely an option for layers.</div>
    </blockquote>
    <br>
    Nothing  wrong in having maintainers listed somewhere. The more
    important part IMHO,  is the UPSTREAM_CHECK_*  part.<br>
    <blockquote type="cite"
cite="mid:CAJTo0LaHk+CcKw_ayGWD0n=ycqnCLewx4F531Y5MTvn-OnOoVw@mail.gmail.com">
      <div dir="ltr"><br>
        <div>For core, we should be requiring it yes.  UPSTREAM_CHECK_*
          don't *need* to be present as there are defaults, </div>
      </div>
    </blockquote>
    <br>
    defaults? <br>
    <br>
    <blockquote type="cite"
cite="mid:CAJTo0LaHk+CcKw_ayGWD0n=ycqnCLewx4F531Y5MTvn-OnOoVw@mail.gmail.com">
      <div dir="ltr">
        <div>what we should start checking regularly is that checkpkg
          works (and the selftest does spot most of the failures).</div>
      </div>
    </blockquote>
    <br>
    The side benefit is we start getting these changes into other layers
    so checkpkg can be utilized by other maintainers.<br>
    <br>
    - armin<br>
    <blockquote type="cite"
cite="mid:CAJTo0LaHk+CcKw_ayGWD0n=ycqnCLewx4F531Y5MTvn-OnOoVw@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>Ross<br>
          <div><br>
          </div>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On 25 February 2018 at 22:39,
          akuster808 <span dir="ltr">&lt;<a
              href="mailto:akuster808@gmail.com" target="_blank"
              moz-do-not-send="true">akuster808@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">I think
            its time we entertain updating new applications and package<br>
            updates submissions process.<br>
            <br>
            If a new package is being added or updated,  we should
            expect<br>
            "UPSTREAM_CHECK_REGEX" to be present. Maybe even include an
            entry to the<br>
            mainainers.inc file?<br>
            <br>
            This could apply to all layers.<br>
            <br>
            <br>
            What do you thing?<br>
            <br>
            Mahalo,<br>
            <br>
            armin<br>
            <br>
            <br>
            ______________________________<wbr>_________________<br>
            Openembedded-architecture mailing list<br>
            <a
              href="mailto:Openembedded-architecture@lists.openembedded.org"
              moz-do-not-send="true">Openembedded-architecture@<wbr>lists.openembedded.org</a><br>
            <a
href="http://lists.openembedded.org/mailman/listinfo/openembedded-architecture"
              rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>architecture</a><br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>