Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Schwan <m.schwan@phytec.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][PATCH v2] python-waitress: Add recipes
Date: Thu, 24 Oct 2019 13:38:26 +0200	[thread overview]
Message-ID: <84402ad74c6fc2da7db63f59d9082c35b6686ee4.camel@phytec.de> (raw)
In-Reply-To: <20191009123218.19821-1-m.schwan@phytec.de>

Hi,

just wanted to kindly ask if anyone had time reviewing this patch? This
is my first patch for this project, maybe I am missing something. Is
there anything that stops this from being merged?

On Wed, 2019-10-09 at 14:32 +0200, Martin Schwan wrote:
> Waitress is a pure-Python WSGI server.
> 
> Signed-off-by: Martin Schwan <m.schwan@phytec.de>
> ---
> Changes in v2:
>  - Fixed missing "K" in "LIC_FILES_CHKSUM"
> ---
>  .../recipes-devtools/python/python-waitress.inc        | 10 ++++++++++
>  .../recipes-devtools/python/python-waitress_1.3.1.bb   |  2 ++
>  .../recipes-devtools/python/python3-waitress_1.3.1.bb  |  2 ++
>  3 files changed, 14 insertions(+)
>  create mode 100644 meta-python/recipes-devtools/python/python-waitress.inc
>  create mode 100644 meta-python/recipes-devtools/python/python-waitress_1.3.1.bb
>  create mode 100644 meta-python/recipes-devtools/python/python3-waitress_1.3.1.bb
> 
> diff --git a/meta-python/recipes-devtools/python/python-waitress.inc b/meta-python/recipes-devtools/python/python-waitress.inc
> new file mode 100644
> index 000000000..732c31dbd
> --- /dev/null
> +++ b/meta-python/recipes-devtools/python/python-waitress.inc
> @@ -0,0 +1,10 @@
> +SUMMARY = "A WSGI server for Python"
> +DESCRIPTION = "Waitress is meant to be a production-quality pure-Python WSGI \
> +    server with very acceptable performance."
> +HOMEPAGE = "https://github.com/Pylons/waitress"
> +SECTION = "devel/python"
> +LICENSE = "ZPL-2.1"
> +LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=78ccb3640dc841e1baecb3e27a6966b2"
> +
> +SRC_URI[md5sum] = "d9132d313de0c5e0fec34ef9ede5442e"
> +SRC_URI[sha256sum] = "278e09d6849acc1365404bbf7d790d0423b159802e850c726e8cd0a126a2dac7"
> diff --git a/meta-python/recipes-devtools/python/python-waitress_1.3.1.bb b/meta-python/recipes-devtools/python/python-waitress_1.3.1.bb
> new file mode 100644
> index 000000000..26a628ea0
> --- /dev/null
> +++ b/meta-python/recipes-devtools/python/python-waitress_1.3.1.bb
> @@ -0,0 +1,2 @@
> +inherit setuptools pypi
> +require python-waitress.inc
> diff --git a/meta-python/recipes-devtools/python/python3-waitress_1.3.1.bb b/meta-python/recipes-devtools/python/python3-waitress_1.3.1.bb
> new file mode 100644
> index 000000000..83c8b66d8
> --- /dev/null
> +++ b/meta-python/recipes-devtools/python/python3-waitress_1.3.1.bb
> @@ -0,0 +1,2 @@
> +inherit setuptools3 pypi
> +require python-waitress.inc
> -- 
> 2.23.0
> 



  reply	other threads:[~2019-10-24 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 12:32 [meta-python][PATCH v2] python-waitress: Add recipes Martin Schwan
2019-10-24 11:38 ` Martin Schwan [this message]
2019-10-24 12:46   ` Khem Raj
2019-10-24 23:00     ` Khem Raj
2019-10-25  7:39       ` Martin Schwan
2019-10-25  9:08         ` Khem Raj
2019-10-25 17:46           ` Randy MacLeod
2019-10-25 17:59             ` Khem Raj

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=84402ad74c6fc2da7db63f59d9082c35b6686ee4.camel@phytec.de \
    --to=m.schwan@phytec.de \
    --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