<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 02/02/2013 03:08 AM, Bruce Ashfield
      wrote:<br>
    </div>
    <blockquote
cite="mid:CADkTA4OuDqRE25oNRbFJCyrWpkkj62HpHHNN4qOFocNnrgSY_w@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">On Fri, Feb 1, 2013 at 1:56 PM, Saul
            Wold <span dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:sgw@linux.intel.com" target="_blank">sgw@linux.intel.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 class="im">On 02/01/2013 06:18 AM, Bruce Ashfield
                wrote:<br>
              </div>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div class="im">
                  <br>
                  <br>
                  <br>
                  On Fri, Feb 1, 2013 at 4:00 AM, &lt;<a
                    moz-do-not-send="true"
                    href="mailto:Qi.Chen@windriver.com" target="_blank">Qi.Chen@windriver.com</a><br>
                </div>
                &lt;mailto:<a moz-do-not-send="true"
                  href="mailto:Qi.Chen@windriver.com" target="_blank">Qi.Chen@windriver.com</a>&gt;&gt;
                wrote:<br>
                <br>
                &nbsp; &nbsp; From: Chen Qi &lt;<a moz-do-not-send="true"
                  href="mailto:Qi.Chen@windriver.com" target="_blank">Qi.Chen@windriver.com</a>
                &lt;mailto:<a moz-do-not-send="true"
                  href="mailto:Qi.Chen@windriver.com" target="_blank">Qi.Chen@windriver.com</a>&gt;&gt;
                <div class="im">
                  <br>
                  <br>
                  &nbsp; &nbsp; Add config fragments to busybox.<br>
                  <br>
                  &nbsp; &nbsp; Both the implementation and the use case are
                  similar to yocto kernel's<br>
                  &nbsp; &nbsp; configuration fragments.<br>
                  <br>
                  <br>
                  I can fairly easily tweak the configuration parts of
                  the kern-tools to<br>
                  handle this<br>
                  use case as well. That would allow us to re-use the
                  kernel's merge_config.sh<br>
                  script (with a minor dependency change) and save some
                  duplicated code. It<br>
                  also gets you the advantage that you can consolidate
                  configuration fragments<br>
                  outside of any build system, which isn't as critical
                  here, but something<br>
                  that<br>
                  is used quite a bit during kernel testing.<br>
                  <br>
                </div>
              </blockquote>
              Bruce,<br>
              <br>
              Where is the merge_config.sh script today? &nbsp;Would you
              propose moving it to the scripts dir and have the busybox
              recipe call it?<br>
            </blockquote>
            <div><br>
            </div>
            <div style="">It's part of the mainline kernel, hence why
              grabbing the guts out of it reproducing&nbsp;</div>
            <div style="">it here isn't the best idea, we'll have a need
              to keep them in sync. In fact, I have</div>
            <div style="">2 or 3 pending patches for it in the
              kern-tools repository that I need to get upstream</div>
            <div style="">
              (as an example).</div>
            <div style=""><br>
            </div>
            <div style="">I'd propose either creating a separate recipe
              for it (i.e. like kconfig-frontends) or I could</div>
            <div style="">keep it in kern-tools (badly named, but we can
              work on that ;) and maintain / coordinate</div>
            <div style="">changes to it.</div>
            <div style=""><br>
            </div>
            <div style="">I just don't want to see the effort happen
              twice, we are busy enough!</div>
            <div>&nbsp;</div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <br>
              What would be your timing on making such a change, ie hold
              this patch until your get it merge or merge this and then
              fix it when you merge your changes?<br>
            </blockquote>
            <div><br>
            </div>
            <div style="">I could feasibly get it done in the next few
              weeks, the changes aren't bug, I just</div>
            <div style="">have to avoid regressions on either side
              (kernel or busy box).&nbsp;</div>
            <div style=""><br>
            </div>
            <div style="">That being said, the interface to the SRC_URI
              is the same for the two, so if we are</div>
            <div style="">ok with me arriving and removing the in-recipe
              support, I guess I can't object too</div>
            <div style="">much :) The only risk is that if anyone starts
              using this first support immediately,&nbsp;</div>
            <div style="">I do risk regressing their use case, where if
              it never goes in, that won't happen.</div>
            <div style=""><br>
            </div>
            <div style="">Cheers,</div>
            <div style=""><br>
            </div>
            <div style="">Bruce</div>
            <div style=""><br>
            </div>
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Hi Bruce,<br>
    <br>
    I just tried to reuse the kernel's merge_config.sh script, and it
    turned out well.<br>
    The patch is in attachment.<br>
    <br>
    Is it enough for now?<br>
    If so, I'll send out the patch.<br>
    <br>
    Thanks,<br>
    Chen Qi<br>
  </body>
</html>