On Mon, Jan 20, 2020 at 7:15 PM Denys Dmytriyenko <denis@...> wrote:
On Fri, Jan 17, 2020 at 09:55:55PM +0100, Andreas Müller wrote:
On Fri, Jan 17, 2020 at 9:21 PM Denys Dmytriyenko <denis@...> wrote:Don't worry about that, let's file it under "overreaction due to stress"
On Fri, Jan 17, 2020 at 09:15:09PM +0100, Andreas M?ller wrote:
On Fri, Jan 17, 2020 at 7:35 PM Khem Raj <raj.khem@...> wrote:What, not calling it the worst patch of the year? And the year's just
Just a question: What is the plan with all those recipes which are
perhaps add them to meta-py2 first before this lands
going to fail (most headaches I have with old waf): Will meta-oe /
meta-networking..., depend on meta-py2 or kick them out or?
1. Would you accept an apologize for that one?
category, shall we? :)
2. I did not ask for stopping this - just asked how to continue and IYes, all good points. I would agree with Khem - let's drop it and try to
did that for certain reasons: For example: Few minutes ago we saw a
series for npm rework on oe-core. Unfortunately npm as is requires
python2 and many modules. Or the waf stuff: That means somebody has go
to all the projects and ask them for waf upgrade or prepare patches
there (and that means not just upgrading waf). So again: How do we
handle/get rid recipes requiring python2 to build?
fix as many issues as possible, while we still have time until the release.
Distros can have own dependency on meta-python2, but meta-openembedded and
openembedded-core should not depend on deprecated components, IMHO.