From: Tim Orling <timothy.t.orling@linux.intel.com>
To: Alejandro Hernandez <alejandro.hernandez@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: Fri, 24 Nov 2017 22:04:32 -0700 [thread overview]
Message-ID: <0A2583BA-1CFF-4687-A22A-AAAB8FF39E11@linux.intel.com> (raw)
In-Reply-To: <7079b2e6-b0e8-7882-9b7a-e8bafd94f78c@linux.intel.com>
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-25 5:04 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 [this message]
2017-11-25 23:45 ` Alejandro Hernandez
2017-11-26 2:08 ` Alejandro Hernandez
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=0A2583BA-1CFF-4687-A22A-AAAB8FF39E11@linux.intel.com \
--to=timothy.t.orling@linux.intel.com \
--cc=alejandro.hernandez@linux.intel.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 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.