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 3D78C1381F3 for ; Sun, 20 Oct 2013 16:26:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 335C0E0A00; Sun, 20 Oct 2013 16:26:54 +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 97F17E0A00 for ; Sun, 20 Oct 2013 16:26:53 +0000 (UTC) Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (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 7A3ED33ED70 for ; Sun, 20 Oct 2013 16:26:52 +0000 (UTC) Received: by mail-ie0-f170.google.com with SMTP id at1so9978736iec.1 for ; Sun, 20 Oct 2013 09:26:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=w7lEzN7O6hAeUHKD2wMtVdYD0GC9Bwqy1Vapoj3dvYQ=; b=GcXjwuVOABnh3/OY4qKGeFx0kPLzxnbL4WovI2ypYrgDNgymg9I1hIBvyFOpe/B4FN WXittSOlm7QTHKmA3mBNFVifKgDmHfeOgVvh0AiEdwlIfAxu4/fS6ScebXGFeEX+iB1F mDnLvX7T0Qn9ZhJ1xNgB72oIdGvyhmZ/1u33+LKhp73kWdGyd4gug4psAZvZyMzyX1nv xWadWp0t9QMnLc3cBFQz+K/s8ppLup35x2qRdn37EBJpmTcSYBg7xKGhCxIlZoZFq8Bk OiRNFAiZlzhU61G22zQx0YM1IljzFEvs5zOgtrAJ8eDtX/ZwSFotuOxzUfJx/OWwyLml pG6g== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Discussions centering around the Python ecosystem in Gentoo Linux X-BeenThere: gentoo-python@gentoo.org X-BeenThere: gentoo-python@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.50.170.225 with SMTP id ap1mr6441285igc.47.1382286411069; Sun, 20 Oct 2013 09:26:51 -0700 (PDT) Received: by 10.64.139.5 with HTTP; Sun, 20 Oct 2013 09:26:51 -0700 (PDT) In-Reply-To: <20131020174723.55105549@gentoo.org> References: <1382254606-26643-1-git-send-email-mgorny@gentoo.org> <20131020171216.7642328f@gentoo.org> <20131020174723.55105549@gentoo.org> Date: Sun, 20 Oct 2013 12:26:51 -0400 Message-ID: Subject: Re: [gentoo-python] [PATCH] Introduce python_setup() as a common name for Python setup function. From: Mike Gilbert To: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= Cc: gentoo-python Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 0dae5f2f-d399-44c2-a630-712ac89a1f1f X-Archives-Hash: ff86052ff2271f82c43082f20bdfeb89 On Sun, Oct 20, 2013 at 11:47 AM, Micha=C5=82 G=C3=B3rny wrote: > Dnia 2013-10-20, o godz. 11:33:45 > Mike Gilbert napisa=C5=82(a): > >> On Sun, Oct 20, 2013 at 11:12 AM, Micha=C5=82 G=C3=B3rny wrote: >> > Dnia 2013-10-20, o godz. 10:53:34 >> > Mike Gilbert napisa=C5=82(a): >> > >> >> On Sun, Oct 20, 2013 at 3:36 AM, Micha=C5=82 G=C3=B3rny wrote: >> >> > As described in the ml, the new function does: >> >> > >> >> > * in python-any-r1, choose and set up the best installed impl, >> >> > >> >> > * in python-single-r1, read PYTHON_SINGLE_TARGET and set it up, >> >> > >> >> > * in python-r1, call python_export_best + python_wrapper_setup. >> >> > >> >> > In other words, it's a common way of getting Python build environme= nt >> >> > set up in the ebuild scope. >> >> >> >> Invoking python_setup from pkg_setup in any eclass seems sub-optimal; >> >> especially so in python-any-r1. However, I realize there isn't a grea= t >> >> place to put it. >> > >> > I don't understand. Could you rephrase? >> > >> >> The python stuff is generally only used in "src" phases, so pkg_setup >> is the wrong place for it.. As well, it would be better to set up the >> python wrappers and environment in a phase where the sandbox and >> userpriv are active to prevent permissions problems like we had with >> Paludis recently (there's a bug, but I'm not going to look for it). > > I can understand you but can't really think of a good way of doing > this. The only other reasonable phase for this is src_prepare(), > and overriding it will result in hell breaking loose... > Right. I just wanted to go "on the record" as saying that this is not optimal, but there is probably no better alternative. Carry on. ^_^