From: "Adrian Bunk" <bunk@stusta.de>
To: Steve Sakoman <sakoman@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
Denys Dmytriyenko <denis@denix.org>,
Joshua Watt <jpewhacker@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
jdmason@kudzu.us, Khem Raj <raj.khem@gmail.com>
Subject: Re: [OE-core][PATCH 0/4] Import recipes from meta-python
Date: Sat, 16 May 2020 20:47:02 +0300 [thread overview]
Message-ID: <20200516174702.GA22042@localhost> (raw)
In-Reply-To: <CAGDS+n=_mqZeLFusTNV6s7EKNBDVdM589wAmcJ5qQH2BMn=MLw@mail.gmail.com>
On Fri, May 15, 2020 at 03:21:57PM -1000, Steve Sakoman wrote:
>
> I'm seeing a few votes of "yes for dunfell" and no opposition as yet
> (at least here on the list).
>
> I support the desire to get rid of a meta-python dependency in bsp
> layers so I'm also a yes vote unless someone comes up with a good
> reason why we shouldn't.
meta-openembedded/meta-python has a higher layer priority than OE-core.
Adding higher upstream versions of these recipes to a lower-priority
layer in a stable series is a potential source for weird problems.
> Steve
cu
Adrian
next prev parent reply other threads:[~2020-05-16 17:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 21:04 [OE-core][PATCH 0/4] Import recipes from meta-python Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 1/4] pycryptodome: Import " Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 2/4] pyelftools: " Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 3/4] python3-pycryptodome(x): Upgrade 3.9.4 -> 3.9.7 Joshua Watt
2020-05-14 21:04 ` [OE-core][PATCH 4/4] python3-pyelftools: Upgrade 0.25 -> 0.26 Joshua Watt
2020-05-15 18:53 ` [OE-core][PATCH 0/4] Import recipes from meta-python Denys Dmytriyenko
2020-05-15 19:05 ` Richard Purdie
2020-05-15 19:12 ` Joshua Watt
2020-05-15 19:26 ` Denys Dmytriyenko
2020-05-15 19:56 ` Andrey Zhizhikin
2020-05-15 19:32 ` Khem Raj
2020-05-17 1:05 ` Alejandro Hernandez
2020-05-16 1:21 ` Steve Sakoman
2020-05-16 17:47 ` Adrian Bunk [this message]
2020-05-16 19:54 ` Peter Kjellerstedt
2020-05-16 20:09 ` Adrian Bunk
2020-05-16 20:24 ` Andrey Zhizhikin
2020-05-16 23:15 ` Andre McCurdy
2020-05-17 13:22 ` Adrian Bunk
2020-05-17 13:56 ` Martin Jansa
2020-05-17 15:45 ` Adrian Bunk
2020-05-17 16:00 ` Martin Jansa
2020-05-17 16:14 ` Adrian Bunk
2020-05-17 23:47 ` Khem Raj
2020-05-19 18:20 ` Steve Sakoman
2020-05-19 18:24 ` Martin Jansa
2020-05-19 19:57 ` Andre McCurdy
2020-05-21 9:11 ` Martin Jansa
2020-05-17 23:45 ` Khem Raj
2020-05-17 23:41 ` Khem Raj
2020-05-18 6:41 ` Alejandro Hernandez
2020-05-17 23:38 ` Khem Raj
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=20200516174702.GA22042@localhost \
--to=bunk@stusta.de \
--cc=denis@denix.org \
--cc=jdmason@kudzu.us \
--cc=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=sakoman@gmail.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 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.