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 E098E138301 for ; Sun, 27 Oct 2013 02:18:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0C0DCE0AC4; Sun, 27 Oct 2013 02:18:20 +0000 (UTC) Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.182]) by pigeon.gentoo.org (Postfix) with ESMTP id 0B104E0AAB for ; Sun, 27 Oct 2013 02:18:18 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFMCof9/2dsb2JhbABEvw4Xc4IeAQEEATocHAwLCyETEg8FJTeICwbBLY1hgkhhA41+iA6FfohwgV6DEw X-IPAS-Result: Av4EABK/CFFMCof9/2dsb2JhbABEvw4Xc4IeAQEEATocHAwLCyETEg8FJTeICwbBLY1hgkhhA41+iA6FfohwgV6DEw X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="36432775" Received: from 76-10-135-253.dsl.teksavvy.com (HELO waltdnes.org) ([76.10.135.253]) by ironport2-out.teksavvy.com with SMTP; 26 Oct 2013 22:18:17 -0400 Received: by waltdnes.org (sSMTP sendmail emulation); Sat, 26 Oct 2013 22:18:11 -0400 From: "Walter Dnes" Date: Sat, 26 Oct 2013 22:18:11 -0400 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] did python-r1 improve user experience? Message-ID: <20131027021810.GA15388@waltdnes.org> References: <5267CB83.3000306@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 8cbae83f-b01d-47fc-a6d9-77ac40b90ad0 X-Archives-Hash: c6d0bc71b23c29c453a157b9ce4d5336 On Sat, Oct 26, 2013 at 09:30:57PM -0400, Mike Gilbert wrote > The (non-)relationship between eselect python and PYTHON_TARGETS is > something that would be nice to resolve, but I don't know how to do > it. PYTHON_SINGLE_TARGET will probably cause problems if/when packages > start supporting python3 only. What I find interesting/annoying is that my make.conf has to have 3 lines... PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" USE_PYTHON="2.7" ...as if it didn't hear me the first time. How difficult would it be to set up an eclass to tell portage that... if PYTHON_SINGLE_TARGET="pythonX_Y" PYTHON_TARGETS defaults to "${PYTHON_SINGLE_TARGET}" USE_PYTHON defaults to "${PYTHON_SINGLE_TARGET/_/.}" Over-ride the default if explicitly listed. Out of sheer curiousity, what circumstances are there where ordinary users would need differing values for these 3 items? -- Walter Dnes I don't run "desktop environments"; I run useful applications