From: Bill Randle <bill.randle@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-python][V2 PATCH 09/12] python-visitor: move core of recipe to a .inc file
Date: Thu, 7 Dec 2017 21:45:45 -0800 [thread overview]
Message-ID: <20171208054548.26218-10-bill.randle@gmail.com> (raw)
In-Reply-To: <20171208054548.26218-1-bill.randle@gmail.com>
Signed-off-by: Bill Randle <bill.randle@gmail.com>
---
meta-python/recipes-devtools/python/python-visitor.inc | 6 ++++++
meta-python/recipes-devtools/python/python-visitor_0.1.3.bb | 8 +-------
2 files changed, 7 insertions(+), 7 deletions(-)
create mode 100644 meta-python/recipes-devtools/python/python-visitor.inc
diff --git a/meta-python/recipes-devtools/python/python-visitor.inc b/meta-python/recipes-devtools/python/python-visitor.inc
new file mode 100644
index 0000000..8c2288c
--- /dev/null
+++ b/meta-python/recipes-devtools/python/python-visitor.inc
@@ -0,0 +1,6 @@
+SUMMARY = "A tiny pythonic visitor implementation."
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://PKG-INFO;beginline=8;endline=8;md5=8227180126797a0148f94f483f3e1489"
+
+SRC_URI[md5sum] = "94a024ed0ec1b02b4497c15267d319ca"
+SRC_URI[sha256sum] = "2c737903b2b6864ebc6167eef7cf3b997126f1aa94bdf590f90f1436d23e480a"
diff --git a/meta-python/recipes-devtools/python/python-visitor_0.1.3.bb b/meta-python/recipes-devtools/python/python-visitor_0.1.3.bb
index 1236506..eee25a5 100644
--- a/meta-python/recipes-devtools/python/python-visitor_0.1.3.bb
+++ b/meta-python/recipes-devtools/python/python-visitor_0.1.3.bb
@@ -1,8 +1,2 @@
-SUMMARY = "A tiny pythonic visitor implementation."
-LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://PKG-INFO;beginline=8;endline=8;md5=8227180126797a0148f94f483f3e1489"
-
-SRC_URI[md5sum] = "94a024ed0ec1b02b4497c15267d319ca"
-SRC_URI[sha256sum] = "2c737903b2b6864ebc6167eef7cf3b997126f1aa94bdf590f90f1436d23e480a"
-
inherit pypi setuptools
+require python-visitor.inc
--
2.7.4
next prev parent reply other threads:[~2017-12-08 5:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 5:45 [meta-python][V2 PATCH 00/12] Create Python3 recipies for several existing Python2 recipes Bill Randle
2017-12-08 5:45 ` [meta-python][V2 PATCH 01/12] python-dominate: move core of recipe to a .inc file Bill Randle
2017-12-08 5:45 ` [meta-python][V2 PATCH 02/12] python3-dominate: new recipe Bill Randle
2017-12-08 5:45 ` [meta-python][V2 PATCH 03/12] python-flask-bootstrap: move core of recipe to a .inc file Bill Randle
2017-12-08 5:45 ` [meta-python][V2 PATCH 04/12] python3-flask-bootstrap: new recipe Bill Randle
2017-12-08 5:45 ` [meta-python][V2 PATCH 05/12] python-flask-sqlalchemy: move core of recipe to a .inc file Bill Randle
2017-12-08 5:45 ` [meta-python][V2 PATCH 06/12] python3-flask-sqlalchemy: new recipe Bill Randle
2017-12-08 5:45 ` [meta-python][V2 PATCH 07/12] python-flask-wtf: move core of recipe to a .inc file Bill Randle
2017-12-08 5:45 ` [meta-python][V2 PATCH 08/12] python3-flask-wtf: new recipe Bill Randle
2017-12-08 5:45 ` Bill Randle [this message]
2017-12-08 5:45 ` [meta-python][V2 PATCH 10/12] python3-visitor: " Bill Randle
2017-12-08 5:45 ` [meta-python][V2 PATCH 11/12] python-wtforms: move core of recipe to a .inc file Bill Randle
2017-12-08 5:45 ` [meta-python][V2 PATCH 12/12] python3-wtforms: new recipe Bill Randle
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=20171208054548.26218-10-bill.randle@gmail.com \
--to=bill.randle@gmail.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox