From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [v3][PATCH] bind: update to 9.12.1
Date: Sun, 17 Jun 2018 22:36:18 +0100 [thread overview]
Message-ID: <313ce6af489a9ab4bb32f658aa17a251204ea53c.camel@linuxfoundation.org> (raw)
In-Reply-To: <74bb7fdc-8e9d-dd2d-c150-6d6b6ab79770@gmail.com>
On Sun, 2018-06-17 at 14:28 -0700, akuster808 wrote:
> > > Requires python-ply package in core
> >
> > Comment says use meta-python. If the python code here is useful,
> > we
> > can add it to core.
>
> its in master now... I think..
Its in master-next, pending us figuring this other patch out.
> > Conflicts with the commit message. Pick one.
> >
> > > +PACKAGECONFIG[python3] = "--with-python=${PYTHON}, --without-
> > > python, python3-native python3-ply-native, python3-core"
> >
> > Just python3-core sounds unlikely as that's a subset of the
> > standard library.
>
> I just noticed python3-ply does not exist in the patch I sent you so
> I have done a v2 for that python-ply package.
Can you check what is in -next please as that was my fixed up version
of your patch which does what it says (and fixes maintainers too).
Do we need both the py2 and py3 versions?
Cheers,
Richard
next prev parent reply other threads:[~2018-06-17 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 14:11 [v3][PATCH] bind: update to 9.12.1 Armin Kuster
2018-06-11 14:53 ` akuster808
2018-06-15 16:53 ` Burton, Ross
2018-06-17 21:28 ` akuster808
2018-06-17 21:36 ` Richard Purdie [this message]
2018-06-18 14:42 ` akuster808
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=313ce6af489a9ab4bb32f658aa17a251204ea53c.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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