From: "Michał Górny" <mgorny@gentoo.org>
To: Mike Gilbert <floppym@gentoo.org>
Cc: gentoo-python <gentoo-python@lists.gentoo.org>
Subject: Re: [gentoo-python] [PATCH] Introduce python_setup() as a common name for Python setup function.
Date: Sun, 20 Oct 2013 17:47:23 +0200 [thread overview]
Message-ID: <20131020174723.55105549@gentoo.org> (raw)
In-Reply-To: <CAJ0EP41cKTnXgpKUb+soKpr12TUt0tMx4wOSg2dCV8=DO=tu8A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
Dnia 2013-10-20, o godz. 11:33:45
Mike Gilbert <floppym@gentoo.org> napisał(a):
> On Sun, Oct 20, 2013 at 11:12 AM, Michał Górny <mgorny@gentoo.org> wrote:
> > Dnia 2013-10-20, o godz. 10:53:34
> > Mike Gilbert <floppym@gentoo.org> napisał(a):
> >
> >> On Sun, Oct 20, 2013 at 3:36 AM, Michał Górny <mgorny@gentoo.org> 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 environment
> >> > 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 great
> >> 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...
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-10-20 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 7:36 [gentoo-python] [PATCH] Introduce python_setup() as a common name for Python setup function Michał Górny
2013-10-20 14:53 ` Mike Gilbert
2013-10-20 15:12 ` Michał Górny
2013-10-20 15:33 ` Mike Gilbert
2013-10-20 15:47 ` Michał Górny [this message]
2013-10-20 16:26 ` Mike Gilbert
2013-10-22 15:18 ` Michał Górny
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=20131020174723.55105549@gentoo.org \
--to=mgorny@gentoo.org \
--cc=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