From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] distutils3: Avoid MACHINE specific checksums
Date: Wed, 30 Sep 2015 16:56:56 +0100 [thread overview]
Message-ID: <1443628616.5162.119.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0Lb+sOMG0ovH9+u6Xa7R+qQ2UWOc__MCxh8iUzJiD9R9oA@mail.gmail.com>
On Wed, 2015-09-30 at 16:01 +0100, Burton, Ross wrote:
> On 30 September 2015 at 15:43, Martin Jansa <martin.jansa@gmail.com>
> wrote:
> I'm still using that patch and still haven't found any issues
> caused by
> that, but I'm not using python3 recipes (except building them
> in world),
> so it's possible I've just overlooked them.
>
> It's possible that you're installing eg python3-pip into a totally
> wrong directory though, but I'm having a look at this right now and
> have a funny feeling that a lot of this can actually be deleted.
Agreed. I will likely take the patch I've proposed, since it deals with
a real issue but if we can then clean all this up I'd be all in favour.
At the back of my mind was a plan to figure out the various python
module types that maximally stress distutils.bbclass and
setuptools.bbclass and then make sure we have an example of each in
OE-Core so we can put some better regression testing around this too.
Cheers,
Richard
prev parent reply other threads:[~2015-09-30 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 13:54 [PATCH] distutils3: Avoid MACHINE specific checksums Richard Purdie
2015-09-30 14:43 ` Martin Jansa
2015-09-30 15:01 ` Burton, Ross
2015-09-30 15:56 ` Richard Purdie [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=1443628616.5162.119.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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