public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Manuel Rüger" <mrueg@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] dev/mrueg:master commit in: dev-python/zope-event/
Date: Sat, 11 Jul 2015 01:00:41 +0000 (UTC)	[thread overview]
Message-ID: <1436576434.1ed61f6c386fc2341fbe06b1d7d901b7fd0d6355.mrueg@gentoo> (raw)

commit:     1ed61f6c386fc2341fbe06b1d7d901b7fd0d6355
Author:     Manuel Rüger <mrueg <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 11 01:00:34 2015 +0000
Commit:     Manuel Rüger <mrueg <AT> gentoo <DOT> org>
CommitDate: Sat Jul 11 01:00:34 2015 +0000
URL:        https://gitweb.gentoo.org/dev/mrueg.git/commit/?id=1ed61f6c

[dev-python/zope-event] Initial version.

Package-Manager: portage-2.2.20

 dev-python/zope-event/Manifest                |  1 +
 dev-python/zope-event/metadata.xml            |  8 ++++++++
 dev-python/zope-event/zope-event-4.0.3.ebuild | 28 +++++++++++++++++++++++++++
 3 files changed, 37 insertions(+)

diff --git a/dev-python/zope-event/Manifest b/dev-python/zope-event/Manifest
new file mode 100644
index 0000000..5ec280c
--- /dev/null
+++ b/dev-python/zope-event/Manifest
@@ -0,0 +1 @@
+DIST zope.event-4.0.3.tar.gz 390984 SHA256 f5fdf6ca5716f714023358b212f7f435539dea11771603cd90eebf3ad34405f1 SHA512 bc328bb588beea0cdf55d5f36ff5b269d7b75f399b6d595e1df6565bf1d1fbe2d65b63072db26d096a3fc2dfc0fcec747ea7cf8eabe3c4535084347cb149f1e7 WHIRLPOOL 58ce4490fa86c79b30edc3c96d8d9e912b5d692bffe9664a29d2a7963efb90bb6d03acbe0774eb03ac912acfe44cca1c126cc1a840538bd2abcb1848ec972b53

diff --git a/dev-python/zope-event/metadata.xml b/dev-python/zope-event/metadata.xml
new file mode 100644
index 0000000..bfcb697
--- /dev/null
+++ b/dev-python/zope-event/metadata.xml
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+	<maintainer>
+		<email>mrueg@gentoo.org</email>
+		<name>Manuel Rüger</name>
+	</maintainer>
+</pkgmetadata>

diff --git a/dev-python/zope-event/zope-event-4.0.3.ebuild b/dev-python/zope-event/zope-event-4.0.3.ebuild
new file mode 100644
index 0000000..99b7ed6
--- /dev/null
+++ b/dev-python/zope-event/zope-event-4.0.3.ebuild
@@ -0,0 +1,28 @@
+# Copyright 1999-2015 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Header: $
+
+EAPI=5
+PYTHON_COMPAT=(python{2_7,3_3,3_4})
+
+inherit distutils-r1
+MY_PN=zope.event
+
+MY_P=${MY_PN}-${PV}
+DESCRIPTION=" Event publishing / dispatch, used by Zope Component Architecture"
+HOMEPAGE="https://github.com/zopefoundation/zope.event http://docs.zope.org/zope.event/"
+SRC_URI="mirror://pypi/${MY_PN:0:1}/${MY_PN}/${MY_P}.tar.gz"
+
+LICENSE="ZPL"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE="test"
+
+DEPEND="test? ( dev-python/nose[${PYTHON_USEDEP}] )
+	dev-python/setuptools[${PYTHON_USEDEP}]"
+
+S=${WORKDIR}/${MY_P}
+
+python_test() {
+	nosetests || die
+}


             reply	other threads:[~2015-07-11  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11  1:00 Manuel Rüger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-11 14:02 [gentoo-commits] dev/mrueg:master commit in: dev-python/zope-event/ Manuel Rüger
2015-12-01 21:10 Manuel Rüger

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=1436576434.1ed61f6c386fc2341fbe06b1d7d901b7fd0d6355.mrueg@gentoo \
    --to=mrueg@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