From: Richard Purdie <richard.purdie@intel.com>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Jussi Laako <jussi@sonarnerd.net>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [dora]Re: Failure in license.bbclass
Date: Tue, 25 Mar 2014 13:43:36 +0000 [thread overview]
Message-ID: <1395755016.24890.27.camel@ted> (raw)
In-Reply-To: <533147BA.706@windriver.com>
On Tue, 2014-03-25 at 17:09 +0800, Robert Yang wrote:
>
> On 03/13/2014 05:00 PM, Jussi Laako wrote:
> > Hi,
> >
> > On 03/11/2014 12:40 PM, Robert Yang wrote:
> >> It is used for fixing this bug:
> >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=5572
> >>
> >> Enalbe COPY_LIC_MANIFEST and COPY_LIC_DIRS: No kernel license is
> >> installed in image
> >>
> >> But it used the "oe-pkgdata-util lookup-recipe" which is only on master
> >> branch,
> >> I think that we'd better:
> >>
> >> 1) Revert this commit, then it works with minor problems.
> >>
> >> Or
> >>
> >> 2) Fix the "oe-pkgdata-util lookup-recipe" on dora.
> >
> > With core-image-minimal spiced up with couple of packages, there were quite many
> > license directories left empty, so it requires fair amount of manual work to
> > rectify the situation. So it is far more than just the kernel.
> >
> > For example any libraries coming from util-linux, plus any of the gcc runtimes
> > (libgcc, etc). There are many packages where source name doesn't match with the
> > produced packages.
> >
> > Since BSPs tend to lag behind release schedule, option (2) could possibly help
> > quite many...
> >
>
> Thanks, I've talked Hongxu, he will fix it on dora without backport
> the 7 commits, and we need revert this one on dora:
>
> commit e58a1499accd74d3e6fe4f899711d4c680ebc18f
> Author: Hongxu Jia <hongxu.jia@windriver.com>
> Date: Wed Nov 20 18:35:39 2013 +0800
>
> license.bbclass: fix copying license directories failed
>
>
> Paul and RP, what's your opinion, please ?
Seems reasonable to me. We reverted that patch a while ago.
Cheers,
Richard
prev parent reply other threads:[~2014-03-25 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <531ECDCE.3020805@sonarnerd.net>
2014-03-11 9:16 ` [dora]Re: Failure in license.bbclass Hongxu Jia
2014-03-11 10:02 ` Paul Eggleton
2014-03-11 10:40 ` Robert Yang
[not found] ` <532173C2.2000606@sonarnerd.net>
2014-03-25 9:09 ` Robert Yang
2014-03-25 13:43 ` Richard Purdie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1395755016.24890.27.camel@ted \
--to=richard.purdie@intel.com \
--cc=jussi@sonarnerd.net \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox