public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-python@lists.gentoo.org, python@gentoo.org
Subject: [gentoo-python] Re: [PATCH] Pass --build-scripts in out-of-source builds.
Date: Thu, 27 Dec 2012 17:15:52 -0500	[thread overview]
Message-ID: <CAJ0EP41v0tBPJ3pXgVOzmY_1b0n-9PcGs4As7rTAeHSpzCHyjw@mail.gmail.com> (raw)
In-Reply-To: <1356643854-2340-1-git-send-email-mgorny@gentoo.org>

On Thu, Dec 27, 2012 at 4:30 PM, Michał Górny <mgorny@gentoo.org> wrote:
> We're passing --build-lib anyway -- it adds a bit of consistency to
> this. Python appends the language version to the 'scripts' build dir --
> we don't need it, so it makes using the scripts easier.
> ---
>  gx86/eclass/distutils-r1.eclass | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/gx86/eclass/distutils-r1.eclass b/gx86/eclass/distutils-r1.eclass
> index 54c3afd..ceaf6ab 100644
> --- a/gx86/eclass/distutils-r1.eclass
> +++ b/gx86/eclass/distutils-r1.eclass
> @@ -188,6 +188,8 @@ esetup.py() {
>                         --build-base "${BUILD_DIR}"
>                         # using a single directory for them helps us export ${PYTHONPATH}
>                         --build-lib "${BUILD_DIR}/lib"
> +                       # make the ebuild writer lives easier
> +                       --build-scripts "${BUILD_DIR}/scripts"
>                 )
>         fi
>
> --
> 1.8.0.2
>

lgtm


      reply	other threads:[~2012-12-27 22:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-27 21:30 [gentoo-python] [PATCH] Pass --build-scripts in out-of-source builds Michał Górny
2012-12-27 22:15 ` Mike Gilbert [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=CAJ0EP41v0tBPJ3pXgVOzmY_1b0n-9PcGs4As7rTAeHSpzCHyjw@mail.gmail.com \
    --to=floppym@gentoo.org \
    --cc=gentoo-python@lists.gentoo.org \
    --cc=mgorny@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