From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: [gentoo-python] Testing dev-lang/python version bumps
Date: Sat, 21 Apr 2012 21:12:48 -0400 [thread overview]
Message-ID: <4F935B10.1030206@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
I have done some work this evening to integrate the latest versions of
dev-lang/python from Arfrever's Progress overlay into gentoo-x86.
He has done a nice job rebasing the patchsets and updating the ebuilds.
I took this opportunity to simplify the ebuilds a bit. Primarily this
meant stripping out the logic for pre-release snapshots. If anyone
really thinks we should keep this, please speak up.
Python-2.7.3 is already in the tree, but Arfrever indicates it has a
regression for C++ applications that link python. We should probably do
a revbump for that.
If we can get some people testing these that would be great. I would
like to add them to the tree sometime in the next week.
You may find the ebuilds here:
https://bitbucket.org/floppym/python-testing/src/default/dev-lang/python
Or you can clone the overlay for easy installation:
hg clone https://bitbucket.org/floppym/python-testing
The patchsets should be on the gentoo mirrors by the time you read this.
If not, you may find them here:
http://dev.gentoo.org/~floppym/python/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next reply other threads:[~2012-04-22 1:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 1:12 Mike Gilbert [this message]
2012-04-27 13:03 ` [gentoo-python] Testing dev-lang/python version bumps Dirkjan Ochtman
2012-04-27 15:13 ` Mike Gilbert
2012-04-27 16:35 ` Dirkjan Ochtman
2012-04-27 17:17 ` Mike Gilbert
2012-04-27 17:24 ` Mike Gilbert
2012-04-28 17:14 ` Mike Gilbert
2012-04-28 17:53 ` Mike Gilbert
2012-04-30 6:40 ` Dirkjan Ochtman
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=4F935B10.1030206@gentoo.org \
--to=floppym@gentoo.org \
--cc=gentoo-python@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