From: Philip Tricca <flihp@twobit.us>
To: Chris Patterson <cjp256@gmail.com>
Cc: "meta-virtualization@yoctoproject.org"
<meta-virtualization@yoctoproject.org>
Subject: Re: [PATCH 0/2] Xen: start using PACKAGECONFIG
Date: Tue, 05 Nov 2013 09:30:39 -0500 [thread overview]
Message-ID: <5279010F.8080101@twobit.us> (raw)
In-Reply-To: <CABZSBQfuwRW6rKgT3eYeSi76F9di2E5aoGaULOeV6HszPoqjcQ@mail.gmail.com>
Agree. PACKAGECONFIG is still new to me and I didn't realize this was
the net result. I'll send out a patch soon ... unless you beat me to it.
- Philip
On 11/04/2013 09:55 PM, Chris Patterson wrote:
> I would remove xsm from the default PACKAGECONFIG list. As it stands
> with the defaults, the recipe now requires checkpolicy-native (in
> meta-selinux) to build.
>
> Cheers,
> -Chris
>
> On Tue, Oct 29, 2013 at 2:20 PM, Bruce Ashfield
> <bruce.ashfield@gmail.com <mailto:bruce.ashfield@gmail.com>> wrote:
>
> On Mon, Oct 28, 2013 at 6:10 PM, Philip Tricca <flihp@twobit.us
> <mailto:flihp@twobit.us>> wrote:
> > This is a first pass at cleaning up the DEPENDS and do_configure in
> > the xen_4.3.0 recipe. Adding XSM stuff made it clear that directly
> > interacting with DISTRO_FEATURES was the wrong way to do it. That and
> > when Chris and I ment up at LinuxCon he told me I should have used
> > PACKAGECONFIG in the first place :P
>
> :)
>
> >
> > This small patch series is the first step to handling features (like
> > sdl) using PACKAGECONFIG.
>
> Agreed. Small steps are good. This looks fine to me. I grabbed the
> series,
> since no one has offered an objection!
>
> Bruce
>
> >
> > Philip Tricca (2):
> > Convert direct call to ./configure with oe_runconf and EXTRA_OECONF.
> > Use PACKAGECONFIG to deal with XSM policy.
> >
> > recipes-extended/xen/xen_4.3.0.bb <http://xen_4.3.0.bb> | 19
> +++++++++++++++++--
> > 1 file changed, 17 insertions(+), 2 deletions(-)
> >
> > --
> > 1.7.10.4
> >
> > _______________________________________________
> > meta-virtualization mailing list
> > meta-virtualization@yoctoproject.org
> <mailto:meta-virtualization@yoctoproject.org>
> > https://lists.yoctoproject.org/listinfo/meta-virtualization
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> <mailto:meta-virtualization@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-virtualization
>
>
prev parent reply other threads:[~2013-11-05 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 22:10 [PATCH 0/2] Xen: start using PACKAGECONFIG Philip Tricca
2013-10-28 22:10 ` [PATCH 1/2] Convert direct call to ./configure with oe_runconf and EXTRA_OECONF Philip Tricca
2013-10-28 22:10 ` [PATCH 2/2] Use PACKAGECONFIG to deal with XSM policy Philip Tricca
2013-10-29 18:20 ` [PATCH 0/2] Xen: start using PACKAGECONFIG Bruce Ashfield
2013-11-05 2:55 ` Chris Patterson
2013-11-05 14:30 ` Philip Tricca [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=5279010F.8080101@twobit.us \
--to=flihp@twobit.us \
--cc=cjp256@gmail.com \
--cc=meta-virtualization@yoctoproject.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.