From: Jeremy Olexa <darkside@gentoo.org>
To: <gentoo-dev@lists.gentoo.org>, <arfrever@gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/python-openid: python-openid-2.2.4.ebuild
Date: Tue, 29 Jun 2010 02:05:54 +0000 [thread overview]
Message-ID: <48898e163b259e231be01e6bb1d928fe@localhost> (raw)
In-Reply-To: <20100628194227.C34B42C621@corvid.gentoo.org>
On Mon, 28 Jun 2010 19:42:27 +0000 (UTC), "Arfrever Frehtes Taifersar
Arahesis (arfrever)" <arfrever@gentoo.org> wrote:
> arfrever 10/06/28 19:42:27
>
> Modified: python-openid-2.2.4.ebuild
> Log:
> Fix dependencies.
> (Portage version: HEAD/cvs/Linux x86_64)
Is there any reason you are so non-verbose here? 'cvs log' or '$EDITOR
ChangeLog' equally give us no information about your commit. You are
making it hard on other devs in my opinion, I don't think intentionally,
but can't you just use the ChangeLog more?? At least, that is my small
request and I think others feel the same. If not, I will quietly go back
in my corner.
-Jeremy
> Index: python-openid-2.2.4.ebuild
> ===================================================================
> -EAPI="2"
> -
> -NEED_PYTHON="2.5"
> +EAPI="3"
> +PYTHON_DEPEND="2:2.5"
> SUPPORT_PYTHON_ABIS="1"
> +RESTRICT_PYTHON_ABIS="2.4 3.*"
>
> inherit eutils distutils
>
> @@ -22,7 +22,6 @@
> postgres? ( dev-python/psycopg )
> sqlite? ( || ( dev-lang/python[sqlite] >=dev-python/pysqlite-2 ) )"
> DEPEND="${RDEPEND}"
> -RESTRICT_PYTHON_ABIS="3.*"
next parent reply other threads:[~2010-06-28 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100628194227.C34B42C621@corvid.gentoo.org>
2010-06-29 2:05 ` Jeremy Olexa [this message]
2010-06-28 20:26 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/python-openid: python-openid-2.2.4.ebuild Arfrever Frehtes Taifersar Arahesis
2010-06-28 22:54 ` Sebastian Pipping
2010-06-29 2:49 ` Jeremy Olexa
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=48898e163b259e231be01e6bb1d928fe@localhost \
--to=darkside@gentoo.org \
--cc=arfrever@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