Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 1/1] package-index: inherit pythonnative
Date: Fri, 27 Jul 2012 18:32:07 +0800	[thread overview]
Message-ID: <50126E27.4060906@windriver.com> (raw)
In-Reply-To: <5011EC61.3050006@windriver.com>


After talk with Richard, we'd better move the scripts/rpm-createsolvedb.py to
meta/recipes-support/createrepo/createrepo_0.4.11.bb, I will send an update
sooner, the current fix can be a workaround.

// Robert

On 07/27/2012 09:18 AM, Robert Yang wrote:
>
> Hi Richard,
>
> There was something wrong with my mail sever, I resend the answer now.
>
> On 07/24/2012 06:49 PM, Richard Purdie wrote:
>> On Tue, 2012-07-24 at 18:19 +0800, Robert Yang wrote:
>>> The native python binary has been moved from usr/bin/python to
>>> usr/bin/python-native/python, the recipe which needs python-native
>>> should "inherit pythonnative", otherwise there would be errors when the
>>> python script runs.
>>>
>>> [YOCTO #2822]
>>>
>>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>>> ---
>>>   meta/recipes-core/meta/package-index.bb |    2 ++
>>>   1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> Which part of this recipe needs python-native? Shouldn't scripts which
>> need pythonnative be using the path to the python interpreter
>> explicitly?
>>
>
> It is the poky/scripts/rpm-createsolvedb.py which needs python-native,
> I think that if we want to use /path/to/python-native/python to run
> rpm-createsolvedb.py or create a wrapper for it, we should put the
> rpm-createsolvedb.py into a recipe. So I just inherit pythonnative
> in package-index.bb to make it work. I wonder whether this will cause
> something wrong, please?
>
> // Robert
>
>
>> Cheers,
>>
>> Richard
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>




  reply	other threads:[~2012-07-27 10:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 10:19 [PATCH 0/1] package-index: inherit pythonnative Robert Yang
2012-07-24 10:19 ` [PATCH 1/1] " Robert Yang
2012-07-24 10:49   ` Richard Purdie
2012-07-25  3:31     ` Robert Yang
2012-07-27  1:18     ` Robert Yang
2012-07-27 10:32       ` Robert Yang [this message]
2012-08-06  9:29     ` Martin Jansa
2012-08-07 16:57       ` Richard Purdie
2012-08-08  7:58         ` Robert Yang
2012-08-08  8:29           ` Robert Yang

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=50126E27.4060906@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox