From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] license.bbclass: Splitting out licenses
Date: Wed, 27 Jul 2011 00:00:53 +0100 [thread overview]
Message-ID: <1311721253.2344.320.camel@rex> (raw)
In-Reply-To: <CAPhnLPBO+_t-FXdCd5heU7mwz1aQVi45LKhZ3+cBZehgV42QHg@mail.gmail.com>
On Tue, 2011-07-26 at 08:15 -0700, Flanagan, Elizabeth wrote:
> On Tue, Jul 26, 2011 at 7:57 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Mon, 2011-07-25 at 16:24 -0700, Flanagan, Elizabeth wrote:
> >> Adding a bit more functionality here:
> >> 1. Adding some more SPDX Maps to take care of + licenses
> >> 2. Strip out -native and -cross package license wrangling.
> >> If it doesn't go on the image, we shouldn't wrangle it.
> >> 3. Split out the license destination directory to a
> >> IMAGE_NAME time stamped dir in
> >> /tmp/deploy/licenses/${IMAGE_NAME}/<stamp>
> >>
> >> I've removed the handler from my previous Pull as license
> >> manifest needs more discussion and I don't want these
> >> bug fixes to be held up by an added feature.
> >
> > I obviously don't understand this code :/
> >
> > What happens when I run "bitbake core-image-minimal core-image-sato",
> > i.e. when I build two images in one build?
> >
> > I suspect this current approach is flawed and we actually need to
> > postprocess the installed package list after do_rootfs completes at
> > image generation time to build the *real* list based on the installed
> > packages?
> >
>
> Yes. I've found that this approach is definitely flawed. It works
> great for a single image build. Outside of that it acts funny, like
> you mentioned and can return incorrect results. I'm planning on
> revisting this soon.
>
> I'm suspecting that your suggested approach is the way it'll have to
> be. Looking at what is generated by various runs and I see issues.
>
> > This code is obviously still needed as it would provide the basis so the
> > code can get the licenses it needs to pull together...
>
> Yes, agreed.
So with this in mind, where does that put this pull request? :)
Cheers,
Richard
next prev parent reply other threads:[~2011-07-26 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 23:24 [PATCH 1/1] license.bbclass: Splitting out licenses Flanagan, Elizabeth
2011-07-26 14:57 ` Richard Purdie
2011-07-26 15:15 ` Flanagan, Elizabeth
2011-07-26 23:00 ` Richard Purdie [this message]
2011-07-27 18:04 ` Flanagan, Elizabeth
2011-07-29 21:41 ` Cliff Brake
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=1311721253.2344.320.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.