From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 667641381F3 for ; Mon, 8 Apr 2013 01:51:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CF111E0D71; Mon, 8 Apr 2013 01:51:31 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EBFD2E0D68 for ; Mon, 8 Apr 2013 01:51:30 +0000 (UTC) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id D2A3233DC29 for ; Mon, 8 Apr 2013 01:51:29 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id tp5so6287680ieb.22 for ; Sun, 07 Apr 2013 18:51:28 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.50.107.106 with SMTP id hb10mr5413200igb.25.1365385888233; Sun, 07 Apr 2013 18:51:28 -0700 (PDT) Received: by 10.64.102.66 with HTTP; Sun, 7 Apr 2013 18:51:28 -0700 (PDT) In-Reply-To: <87bo9px1pw.fsf@proton.in.awa.tohoku.ac.jp> References: <87bo9px1pw.fsf@proton.in.awa.tohoku.ac.jp> Date: Sun, 7 Apr 2013 21:51:28 -0400 Message-ID: Subject: Re: [gentoo-dev] Python 2.7.4, 3.2.4, 3.3.1 updates From: Mike Gilbert To: Gentoo Dev Cc: Gentoo Python Project Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 3e325c99-8278-443b-b7f0-3b0891264bac X-Archives-Hash: 732cba41929fc2c754ca5109292d0012 On Sun, Apr 7, 2013 at 9:14 PM, heroxbd wrote: > Dear Mike, > > Mike Gilbert writes: > >> This seems like a good opportunity to add slot operator deps and >> remove some prefix workarounds. We can keep an old ebuild around to >> facilitate upgrades if we need to. > > What kind of prefix workaround are you referring to? > Nothing too exciting; just some logic to define EPREFIX in EAPI 2. A simple upgrade to EAPI 3 would suffice for that. > This reminds me that Prefix team is maintaining aqua support (GUI for > Mac OS X) in Python in their own overlay for a long time. I'd like to > see it merged to gx86. If feasible, I am going to run out a patch for > review. > Sounds good to me. Is it something that can be submitted upstream, at least for Python 3.3+?