public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matt Thode" <prometheanfire@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pika-pool/
Date: Fri, 25 Mar 2016 04:29:48 +0000 (UTC)	[thread overview]
Message-ID: <1458880151.bf61c35c5965e49b6144feadc5d0a7d2601540ae.prometheanfire@gentoo> (raw)

commit:     bf61c35c5965e49b6144feadc5d0a7d2601540ae
Author:     Matthew Thode <prometheanfire <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 25 04:28:04 2016 +0000
Commit:     Matt Thode <prometheanfire <AT> gentoo <DOT> org>
CommitDate: Fri Mar 25 04:29:11 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bf61c35c

dev-python/pika-pool: adding for openstack mitaka

Package-Manager: portage-2.2.26

 dev-python/pika-pool/Manifest               |  1 +
 dev-python/pika-pool/metadata.xml           | 11 +++++++++++
 dev-python/pika-pool/pika-pool-0.1.3.ebuild | 21 +++++++++++++++++++++
 3 files changed, 33 insertions(+)

diff --git a/dev-python/pika-pool/Manifest b/dev-python/pika-pool/Manifest
new file mode 100644
index 0000000..d29a11b
--- /dev/null
+++ b/dev-python/pika-pool/Manifest
@@ -0,0 +1 @@
+DIST pika-pool-0.1.3.tar.gz 4722 SHA256 f3985888cc2788cdbd293a68a8b5702a9c955db6f7b8b551aeac91e7f32da397 SHA512 2065e4068310cbf0ac27e3fd242a025a1a174d7faa940cc1eb07b5eb7b7313da2b11456b056fe90520c7a39cec679ee06e38fa3327a6a50548200254d376a62e WHIRLPOOL 35887e2b7ebed7bf10444f389e101343afd36cbc0fb0e30cbce9126f340d146ab2560431e9d9781c7f7eb5eb489bc2e6ceb6b1fc009520c86f77b255de34c844

diff --git a/dev-python/pika-pool/metadata.xml b/dev-python/pika-pool/metadata.xml
new file mode 100644
index 0000000..91e6657
--- /dev/null
+++ b/dev-python/pika-pool/metadata.xml
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+	<maintainer type="person">
+		<email>prometheanfire@gentoo.org</email>
+		<name>Matthew Thode</name>
+	</maintainer>
+	<longdescription lang="en">
+		A connection pool for pika.
+	</longdescription>
+</pkgmetadata>

diff --git a/dev-python/pika-pool/pika-pool-0.1.3.ebuild b/dev-python/pika-pool/pika-pool-0.1.3.ebuild
new file mode 100644
index 0000000..27e18dd
--- /dev/null
+++ b/dev-python/pika-pool/pika-pool-0.1.3.ebuild
@@ -0,0 +1,21 @@
+# Copyright 1999-2016 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=5
+PYTHON_COMPAT=( python2_7 python3_3 python3_4 python3_5 )
+
+inherit distutils-r1
+
+DESCRIPTION="A connection pool for pika."
+HOMEPAGE="https://github.com/bninja/pika-pool"
+SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
+
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="~amd64 ~arm64 ~x86"
+IUSE=""
+
+DEPEND="dev-python/setuptools[${PYTHON_USEDEP}]"
+RDEPEND=">=dev-python/pika-0.9[${PYTHON_USEDEP}]
+	<dev-python/pika-0.11[${PYTHON_USEDEP}]"


             reply	other threads:[~2016-03-25  4:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25  4:29 Matt Thode [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-24 15:24 [gentoo-commits] repo/gentoo:master commit in: dev-python/pika-pool/ Pacho Ramos

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=1458880151.bf61c35c5965e49b6144feadc5d0a7d2601540ae.prometheanfire@gentoo \
    --to=prometheanfire@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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