From: "Arfrever Frehtes Taifersar Arahesis (arfrever)" <arfrever@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in net-zope/zc-buildout: ChangeLog zc-buildout-1.4.2.ebuild
Date: Sun, 01 Nov 2009 23:51:40 +0000 [thread overview]
Message-ID: <E1N4kCy-00066y-8v@stork.gentoo.org> (raw)
arfrever 09/11/01 23:51:40
Modified: ChangeLog
Added: zc-buildout-1.4.2.ebuild
Log:
Version bump.
(Portage version: 14773-svn/cvs/Linux x86_64)
Revision Changes Path
1.2 net-zope/zc-buildout/ChangeLog
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-zope/zc-buildout/ChangeLog?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-zope/zc-buildout/ChangeLog?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-zope/zc-buildout/ChangeLog?r1=1.1&r2=1.2
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/net-zope/zc-buildout/ChangeLog,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ChangeLog 10 Oct 2009 17:03:50 -0000 1.1
+++ ChangeLog 1 Nov 2009 23:51:39 -0000 1.2
@@ -1,6 +1,12 @@
-# ChangeLog for net-zope/zcbuildout
+# ChangeLog for net-zope/zc-buildout
# Copyright 1999-2009 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/net-zope/zc-buildout/ChangeLog,v 1.1 2009/10/10 17:03:50 arfrever Exp $
+# $Header: /var/cvsroot/gentoo-x86/net-zope/zc-buildout/ChangeLog,v 1.2 2009/11/01 23:51:39 arfrever Exp $
+
+*zc-buildout-1.4.2 (02 Nov 2009)
+
+ 02 Nov 2009; Arfrever Frehtes Taifersar Arahesis <arfrever@gentoo.org>
+ +zc-buildout-1.4.2.ebuild:
+ Version bump.
29 Aug 2009; Arfrever Frehtes Taifersar Arahesis <arfrever@gentoo.org>
-zcbuildout-1.2.1.ebuild, -zcbuildout-1.4.1.ebuild, +zc-buildout-1.4.1.ebuild:
1.1 net-zope/zc-buildout/zc-buildout-1.4.2.ebuild
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-zope/zc-buildout/zc-buildout-1.4.2.ebuild?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-zope/zc-buildout/zc-buildout-1.4.2.ebuild?rev=1.1&content-type=text/plain
Index: zc-buildout-1.4.2.ebuild
===================================================================
# Copyright 1999-2009 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/net-zope/zc-buildout/zc-buildout-1.4.2.ebuild,v 1.1 2009/11/01 23:51:39 arfrever Exp $
EAPI="2"
SUPPORT_PYTHON_ABIS="1"
inherit distutils
MY_PN="${PN/-/.}"
MY_P=${MY_PN}-${PV}
DESCRIPTION="System for managing development buildouts"
HOMEPAGE="http://pypi.python.org/pypi/zc.buildout"
SRC_URI="http://pypi.python.org/packages/source/${MY_PN:0:1}/${MY_PN}/${MY_P}.tar.gz"
LICENSE="ZPL"
SLOT="0"
KEYWORDS="~amd64 ~x86"
IUSE=""
RDEPEND="dev-python/setuptools"
DEPEND="${RDEPEND}"
RESTRICT_PYTHON_ABIS="3.*"
S="${WORKDIR}"/${MY_P}
PYTHON_MODNAME="${PN/-//}"
DOCS="CHANGES.txt todo.txt"
src_install() {
distutils_src_install
# Remove README.txt installed in incorrect location.
rm -f "${D}usr/README.txt"
}
reply other threads:[~2009-11-01 23:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1N4kCy-00066y-8v@stork.gentoo.org \
--to=arfrever@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