From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: Tim Orling <timothy.t.orling@linux.intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] python: Restructure python packaging and replace it with autopackaging
Date: Sat, 25 Nov 2017 20:08:54 -0600 [thread overview]
Message-ID: <9ce73c70-d867-a174-7702-e8092dc29fd2@linux.intel.com> (raw)
In-Reply-To: <81105d2c-32f9-8002-2eb2-d9cac0b2fdf8@linux.intel.com>
Hello once again,
I took a look at it and it was no typo, it had no effect on the end
result but it was an actual error on the get_modules script (which I
initially copied from the py2 version, hence the error), fixed and
updated the branch.
Thanks!
Alejandro
On 11/25/2017 05:45 PM, Alejandro Hernandez wrote:
> Hey Tim,
>
>
> Nice catch!, sorry this was an error of mine, but its just a typo,
> must've copied it manually at some point, sorry about that, I fixed it
> and updated the branch!
>
>
> Thanks!
>
>
> Alejandro
>
>
> On 11/24/2017 11:04 PM, Tim Orling wrote:
>> Why does python3-manifest.json contain:
>> + "${libdir}/python2.7/sitecustomize.py”,
>> ?
>>
>>> On Nov 24, 2017, at 4:51 PM, Alejandro Hernandez
>>> <alejandro.hernandez@linux.intel.com> wrote:
>>>
>>> Hey Ross,
>>>
>>>
>>> Yeah sorry, at first I didnt realize why we needed the manifest for
>>> python native, I will fix the commit message.
>>>
>>>
>>> Thanks!
>>>
>>>
>>> Alejandro
>>>
>>> On 11/24/2017 11:06 AM, Burton, Ross wrote:
>>>> On 18 October 2017 at 22:07, Alejandro Hernandez
>>>> <alejandro.hernandez@linux.intel.com> wrote:
>>>> - Removes the manifest from the python-native recipe (Why was it
>>>> there
>>>> in the first place?, native recipes do not get split).
>>>>
>>>> Was this commit written before you added manifest support to
>>>> python-native? :) python-native needs the manifest to set
>>>> RPROVIDES so that dependencies work. Can you update the message?
>>>> (just deleting this line will do)
>>>>
>>>> Ross
>>> --
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2017-11-26 2:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 21:07 [PATCH 0/4] Restructure python2 and python3 packaging system Alejandro Hernandez
2017-10-18 21:07 ` [PATCH 1/4] python: Restructure python packaging and replace it with autopackaging Alejandro Hernandez
2017-11-24 16:57 ` Burton, Ross
2017-11-24 23:49 ` Alejandro Hernandez
2017-11-24 17:06 ` Burton, Ross
2017-11-24 23:51 ` Alejandro Hernandez
2017-11-25 5:04 ` Tim Orling
2017-11-25 23:45 ` Alejandro Hernandez
2017-11-26 2:08 ` Alejandro Hernandez [this message]
2017-10-18 21:07 ` [PATCH 2/4] python3: Restructure python3 " Alejandro Hernandez
2017-11-24 17:05 ` Burton, Ross
2017-11-24 23:50 ` Alejandro Hernandez
2017-10-18 21:07 ` [PATCH 3/4] python3: fix RDEPENDS on several recipes, due to non-existent python3 packages Alejandro Hernandez
2017-10-18 21:07 ` [PATCH 4/4] hwlatdetect: fix RDEPENDS to avoid QA failures Alejandro Hernandez
2017-10-19 20:14 ` ✗ patchtest: failure for Restructure python2 and python3 packaging system (rev2) Patchwork
2017-10-19 20:34 ` Leonardo Sandoval
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=9ce73c70-d867-a174-7702-e8092dc29fd2@linux.intel.com \
--to=alejandro.hernandez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=timothy.t.orling@linux.intel.com \
/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