All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 09/20] python-setuptools: Update for python-native changes
Date: Mon, 16 Jul 2012 09:50:37 +0100	[thread overview]
Message-ID: <1342428637.5019.2.camel@ted> (raw)
In-Reply-To: <1342187709-19368-10-git-send-email-morgan.little@windriver.com>

On Fri, 2012-07-13 at 09:54 -0400, Morgan Little wrote:
> Add pythonnative to the inherits list
> 
> Signed-off-by: Morgan Little <morgan.little@windriver.com>
> ---
>  .../python/python-setuptools_0.6c11.bb             |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/recipes-devtools/python/python-setuptools_0.6c11.bb b/meta/recipes-devtools/python/python-setuptools_0.6c11.bb
> index a769714..dbbc4dc 100644
> --- a/meta/recipes-devtools/python/python-setuptools_0.6c11.bb
> +++ b/meta/recipes-devtools/python/python-setuptools_0.6c11.bb
> @@ -5,7 +5,7 @@ LICENSE = "PSF"
>  LIC_FILES_CHKSUM = "file://setup.py;beginline=23;endline=23;md5=8a314270dd7a8dbca741775415f1716e"
>  
>  SRCNAME = "setuptools"
> -PR = "ml4"
> +PR = "ml3"
>  DEPENDS += "python"
>  DEPENDS_virtclass-native += "python-native"
>  
> @@ -14,7 +14,7 @@ SRC_URI = "\
>  "
>  S = "${WORKDIR}/${SRCNAME}-${PV}"
>  
> -inherit distutils
> +inherit distutils pythonnative

Rather than do this with every user of distutils, would it make sense to
inherit pythonnative in the distutils class? Is there a case we wouldn't
want that inherit?

Cheers,

Richard





  reply	other threads:[~2012-07-16  9:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 13:54 [PATCH 00/20] Change python-native path Morgan Little
2012-07-13 13:54 ` [PATCH 01/20] python-native: Put binaries in seperate directory Morgan Little
2012-07-15  3:06   ` Randy MacLeod
2012-07-13 13:54 ` [PATCH 02/20] python: Update for python-native changes Morgan Little
2012-07-13 13:54 ` [PATCH 03/20] python-dbus: " Morgan Little
2012-07-13 13:54 ` [PATCH 04/20] python-gst: " Morgan Little
2012-07-13 13:54 ` [PATCH 05/20] python-pygobject: " Morgan Little
2012-07-13 13:54 ` [PATCH 06/20] python-pygtk: " Morgan Little
2012-07-13 13:54 ` [PATCH 07/20] python-pyrex-native:Update " Morgan Little
2012-07-13 13:54 ` [PATCH 08/20] python-scons-native: Update " Morgan Little
2012-07-13 13:54 ` [PATCH 09/20] python-setuptools: " Morgan Little
2012-07-16  8:50   ` Richard Purdie [this message]
2012-07-18 20:07     ` Little, Morgan
2012-07-13 13:54 ` [PATCH 10/20] telepathy-glib: " Morgan Little
2012-07-13 13:55 ` [PATCH 11/20] telepathy-python: " Morgan Little
2012-07-13 13:55 ` [PATCH 12/20] libxml2: " Morgan Little
2012-07-13 13:55 ` [PATCH 13/20] mklibs-native: " Morgan Little
2012-07-13 13:55 ` [PATCH 14/20] gnome-doc-utils: " Morgan Little
2012-07-13 13:55 ` [PATCH 15/20] mesa-common: " Morgan Little
2012-07-13 13:55 ` [PATCH 16/20] libxcb: " Morgan Little
2012-07-13 13:55 ` [PATCH 17/20] xcb-proto: " Morgan Little
2012-07-13 13:55 ` [PATCH 18/20] kernelshark: " Morgan Little
2012-07-13 13:55 ` [PATCH 19/20] trace-cmd: " Morgan Little
2012-07-13 13:55 ` [PATCH 20/20] gobject-introspection: " Morgan Little

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=1342428637.5019.2.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.