From: "Michał Górny" <mgorny@gentoo.org>
To: Mike Gilbert <floppym@gentoo.org>
Cc: gentoo-python@lists.gentoo.org, python@gentoo.org
Subject: Re: [gentoo-python] Re: [PATCH] Export best implementation build dir as BUILD_DIR in common phases.
Date: Sat, 12 Jan 2013 22:35:37 +0100 [thread overview]
Message-ID: <20130112223537.2cbfc29d@pomiocik.lan> (raw)
In-Reply-To: <50F1B3BC.6040709@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]
On Sat, 12 Jan 2013 14:04:28 -0500
Mike Gilbert <floppym@gentoo.org> wrote:
> On 01/12/2013 01:52 PM, Michał Górny wrote:
> > This is more friendly than BEST_BUILD_DIR and should not cause trouble
> > in the common cases.
> > ---
> > gx86/eclass/distutils-r1.eclass | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/gx86/eclass/distutils-r1.eclass b/gx86/eclass/distutils-r1.eclass
> > index 8156a36..9d6c714 100644
> > --- a/gx86/eclass/distutils-r1.eclass
> > +++ b/gx86/eclass/distutils-r1.eclass
> > @@ -450,9 +450,11 @@ distutils-r1_run_phase() {
> > # @DESCRIPTION:
> > # Run the given command, restoring the best-implementation state.
> > _distutils-r1_run_common_phase() {
> > + local DISTUTILS_ORIG_BUILD_DIR=${BUILD_DIR}
> > +
> > local EPYTHON=${_DISTUTILS_BEST_IMPL[0]}
> > local PYTHON=${_DISTUTILS_BEST_IMPL[1]}
> > - local BEST_BUILD_DIR=${_DISTUTILS_BEST_IMPL[2]}
> > + local BUILD_DIR=${_DISTUTILS_BEST_IMPL[2]}
> > local PYTHONPATH=${_DISTUTILS_BEST_IMPL[3]}
> >
> > export EPYTHON PYTHON PYTHONPATH
> >
>
> I never really understood the point of BEST_BUILD_DIR anyway. Did
> anything ever use it?
Well, the one ebuild that needed distutils BUILD_DIR.
The major issue is that BUILD_DIR is used in python_foreach_impl to
construct implementation-specific BUILD_DIRs. It's an unlikely scenario
but it will be a bit broken if anything in python_*_all() used
python_foreach_impl() and BUILD_DIR set by it.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
prev parent reply other threads:[~2013-01-12 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 18:52 [gentoo-python] [PATCH] Export best implementation build dir as BUILD_DIR in common phases Michał Górny
2013-01-12 19:04 ` [gentoo-python] " Mike Gilbert
2013-01-12 21:35 ` Michał Górny [this message]
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=20130112223537.2cbfc29d@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=floppym@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=python@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