<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 27, 2013 at 1:26 PM, Paul Eggleton <span dir="ltr"><<a href="mailto:paul.eggleton@linux.intel.com" target="_blank">paul.eggleton@linux.intel.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 class="im">On Wednesday 27 November 2013 12:02:41 Chris Larson wrote:<br>
> Would you mind summarizing the differences between this and the already<br>
> emitted image license manifest in deploy/license?<br>
<br>
</div>Actually I hadn't appreciated that there is a plain package list in that<br>
directory now in addition to the license manifest; however with this version:<br>
<br>
1) It's right next to the image(s) instead of in another directory<br>
<br>
2) The package version is in the same file next to the package name rather than<br>
in a separate file where fields are spread over multiple lines (which is harder<br>
to process)<br>
<br>
3) It includes the package architecture<br>
<br>
4) This isn't for licensing purposes, so it doesn't include any license<br>
information</blockquote></div><br>Understood, thanks. I’ll have to take a look. At Mentor we’ve been using the license manifest coupled with <a href="https://github.com/MentorEmbedded/meta-mentor/blob/master/classes/deploy-license-manifest.bbclass">https://github.com/MentorEmbedded/meta-mentor/blob/master/classes/deploy-license-manifest.bbclass</a>. We’ll probably keep both, use yours for more convenient user examination, and keep the rest for sending off to legal departments and whatnot.<br>
-- <br>Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics
</div></div>