<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 12 February 2016 at 10:40, Gary Thomas <span dir="ltr"><<a href="mailto:gary@mlbassoc.com" target="_blank">gary@mlbassoc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id=":dt" class="" style="overflow:hidden">Policy notwithstanding, there are a lot of lib*-dbg* packages generated<br>
by non-lib* recipes, so my solution doesn't seem so out of place to me.<br></div></blockquote><div><br></div><div>Since da5ec06814e105451cca11cce76b5c5231110524 debug packages are populated automagically into a single PN-dbg unless there's a good rationale (Qt has a good rationale in that one of the libraries embeds WebKit, which makes its debug symbols quite large).</div></div><br></div><div class="gmail_extra">This has been general policy for some time now and whilst other layers may not do this, oe-core doesn't have any recipes that split into multiple dbg packages anymore (afaict).</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>