From: Robert Joslyn <robert.joslyn@redrectangle.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-python][PATCH v2 4/5] python-parse-type: Add Python 3 recipe
Date: Thu, 02 Aug 2018 20:19:49 -0700 [thread overview]
Message-ID: <1533266389.1986.6.camel@redrectangle.org> (raw)
In-Reply-To: <CAMKF1srNOQX4hDPYSr3=nMPdk8dM3o8Z3GToudKbCkd4O8tOgw@mail.gmail.com>
On Thu, 2018-08-02 at 11:11 -0700, Khem Raj wrote:
> On Mon, Jul 30, 2018 at 8:11 PM Robert Joslyn
> <robert.joslyn@redrectangle.org> wrote:
> >
> > Clarify license from BSD to BSD-3-Clause.
> > ---
> > meta-python/recipes-devtools/python/python-parse-type.inc | 12
> > ++++++++++++
> > .../recipes-devtools/python/python-parse-type_0.4.2.bb | 13
> > ++-----------
> > .../recipes-devtools/python/python3-parse-type_0.4.2.bb | 2
> > ++
> > 3 files changed, 16 insertions(+), 11 deletions(-)
> > create mode 100644 meta-python/recipes-devtools/python/python-
> > parse-type.inc
> > create mode 100644 meta-python/recipes-devtools/python/python3-
> > parse-type_0.4.2.bb
> >
> > diff --git a/meta-python/recipes-devtools/python/python-parse-
> > type.inc b/meta-python/recipes-devtools/python/python-parse-
> > type.inc
> > new file mode 100644
> > index 000000000..4549ec98b
> > --- /dev/null
> > +++ b/meta-python/recipes-devtools/python/python-parse-type.inc
> > @@ -0,0 +1,12 @@
> > +SUMMARY = "Simplifies building parse types based on the parse
> > module"
> > +HOMEPAGE = "https://github.com/jenisys/parse_type"
> > +LICENSE = "BSD-3-Clause"
> > +LIC_FILES_CHKSUM =
> > "file://LICENSE;md5=d07323820cca0f1d192cbbf8a0516f95"
> > +
> > +SRC_URI[md5sum] = "b5fa59e45965d1b2896023742df2e707"
> > +SRC_URI[sha256sum] =
> > "f596bdc75d3dd93036fbfe3d04127da9f6df0c26c36e01e76da85adef4336b3c"
> > +
> > +PYPI_PACKAGE = "parse_type"
> > +inherit pypi
> > +
> > +RDEPENDS_${PN} += "${PYTHON_PN}-parse"
>
> there is no recipe for python3-parse but this does mean that
> python3-parse-type will rdep on it and fail the dep check like below
>
> ERROR: Nothing RPROVIDES 'python3-parse' (but
> /mnt/a/oe/sources/meta-openembedded/meta-python/recipes-
> devtools/python/python3-parse-type_0.4.2.bb
> RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'python3-parse' is unbuildable, removing...
I added python3-parse as patch 3 of the series, but that patch got
dropped since another patch to the recipe was pulled in to master
first. I'll resend the series rebased on master, which will fix both
issues.
Thanks,
Robert
> > diff --git a/meta-python/recipes-devtools/python/python-parse-
> > type_0.4.2.bb b/meta-python/recipes-devtools/python/python-parse-
> > type_0.4.2.bb
> > index b516c5912..8e10e801c 100644
> > --- a/meta-python/recipes-devtools/python/python-parse-
> > type_0.4.2.bb
> > +++ b/meta-python/recipes-devtools/python/python-parse-
> > type_0.4.2.bb
> > @@ -1,11 +1,2 @@
> > -SUMMARY = "Simplifies building parse types based on the parse
> > module"
> > -LICENSE = "BSD"
> > -LIC_FILES_CHKSUM =
> > "file://LICENSE;md5=d07323820cca0f1d192cbbf8a0516f95"
> > -PYPI_PACKAGE = "parse_type"
> > -
> > -SRC_URI[md5sum] = "b5fa59e45965d1b2896023742df2e707"
> > -SRC_URI[sha256sum] =
> > "f596bdc75d3dd93036fbfe3d04127da9f6df0c26c36e01e76da85adef4336b3c"
> > -
> > -RDEPENDS_${PN} += "python-parse"
> > -
> > -inherit pypi setuptools
> > +inherit setuptools
> > +require python-parse-type.inc
> > diff --git a/meta-python/recipes-devtools/python/python3-parse-
> > type_0.4.2.bb b/meta-python/recipes-devtools/python/python3-parse-
> > type_0.4.2.bb
> > new file mode 100644
> > index 000000000..91d9ce2d4
> > --- /dev/null
> > +++ b/meta-python/recipes-devtools/python/python3-parse-
> > type_0.4.2.bb
> > @@ -0,0 +1,2 @@
> > +inherit setuptools3
> > +require python-parse-type.inc
> > --
> > 2.16.4
> >
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2018-08-03 3:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 3:09 [meta-python][PATCH v2 0/5] Add python3-behave Recipe Robert Joslyn
2018-07-31 3:09 ` [meta-python][PATCH v2 1/5] python-linecache2: Add recipe Robert Joslyn
2018-07-31 3:09 ` [meta-python][PATCH v2 2/5] python-traceback2: " Robert Joslyn
2018-07-31 3:09 ` [meta-python][PATCH v2 3/5] python-parse: Update to 1.8.4 and add Python 3 version Robert Joslyn
2018-08-02 8:07 ` Khem Raj
2018-07-31 3:09 ` [meta-python][PATCH v2 4/5] python-parse-type: Add Python 3 recipe Robert Joslyn
2018-08-02 18:11 ` Khem Raj
2018-08-03 3:19 ` Robert Joslyn [this message]
2018-07-31 3:09 ` [meta-python][PATCH v2 5/5] python-behave: " Robert Joslyn
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=1533266389.1986.6.camel@redrectangle.org \
--to=robert.joslyn@redrectangle.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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